The Wikimedia Foundation (WMF) section of the village pump is a community-managed page. Editors or Wikimedia Foundation staff may post and discuss information, proposals, feedback requests, or other matters of significance to both the community and the Foundation. It is intended to aid communication, understanding, and coordination between the community and the foundation, though Wikimedia Foundation currently does not consider this page to be a communication venue.
Discussions of proposals which do not require significant foundation attention or involvement belong at Village pump (proposals)
This page is not a place to appeal decisions about article content, which the WMF does not control (except in very rare cases); see Dispute resolution for that.
Issues that do not require project-wide attention should often be handled through Wikipedia:Contact us instead of here.
This board is not the place to report emergencies; go to Wikipedia:Emergency for that.
Threads may be automatically archived after 14 days of inactivity.
Behaviour on this page: This page is for engaging with and discussing the Wikimedia Foundation. Editors commenting here are required to act with appropriate decorum. While grievances, complaints, or criticism of the foundation are frequently posted here, you are expected to present them without being rude or hostile. Comments that are uncivil may be removed without warning. Personal attacks against other users, including employees of the Wikimedia Foundation, will be met with sanctions.
Related: (that last one makes some interesting claims about Wikipedia)
Was this $42K well spent? Who benefited? What was accomplished?
Was this the sort of thing that the donation banners describe your contributions as funding?
Why are some of the links at dead or useless? Are we not capable of posting these publications on WMF servers? --Guy Macon (talk) 18:38, 28 September 2026 (UTC)
Takeaways from the linked paper at [14]:
Theory Section
- The power to shape consensus on Wikipedia is not evenly distributed. Even aside from groups like ArbCom, things like technical knowledge, access to bots, and understanding of the site's jargon gives the small slice of the community with mastery over them ("experienced users") an overwhelming presence in policy discussions.
- The rules pages act as entrenched technical authority that can be used by experienced users against outsiders, not merely as consensus records.
- As proof of the above, most policy pages are very old. If a page survives its first year of official status, it gains enough momentum to be effectively permanent. 11 of the 15 sampled policy pages were fully stabilized by 2011.
- The rules pages are very stable, and that's good. However, they are resistant to change in a way that discourages any new user that isn't already aligned with Wikipedia's way of thinking. Such users don't become experienced users with the ability to shape discussion, and so can't reform the very rules preventing their participation. This is a barrier to gaining new editors from outside the spheres Wikipedia originated in (American male tech nerds).
- Wikipedia's policies, both content and social, can be used as a cudgel against users who threaten local consensus and/or individual editors' worldviews. Examples cited.
- All of the above to say, Wikipedia's current policies fail to reflect actual community consensus due to how they empower users who already agree with them.
There's more stuff about the actual form said empowerment takes, lot of sociology jargon and such. It records the various levels of authority a rules page can have, including unofficial levels like "essay endorsed by popular community members."
Data Section
- The number of individual users involved in creating each policy is very low. It's mostly the same handful of people talking to each other. There were more "critical discursive moments" identified in the sample than unique editors.
- enwiki prefers discussion among a few people with strong opinons and arguments over the flatter voting system of eswiki. The other three languages didn't have much of either, and just kind of trusted whoever was writing the rules.
- Recommendation made that the processes used to define and change policy be adjusted to better reflect actual editor consensus rather than consensus among the technocratically empowered few. No hard suggestion included.
Overall I think it's a useful study, if not for Wikipedia itself then certainly for the history and sociology of internet communities. I'm not mad about it having been funded. ~2026-52337-89 (talk) 23:56, 28 September 2026 (UTC)
The promise (when they were asking for $42K) was "identifying gaps in policy that are necessary for the needs of all English Wikipedians." Please name a gap in policy that was identified, and how we can fix that gap.
Thinking on how to resolve this, perhaps that's the solution - we establish a consensus that donations banners run on enwiki must accurately detail where the money is going. If something is beyond the scope of what donation banners said the WMF is spending money on, then either the WMF needs to cut the program, or not run banners on enwiki. BilledMammal (talk) 02:19, 29 September 2026 (UTC)
@Guy Macon, I don't think expecting research to "succeed" in doing something 100% of the time is a reasonable expectation to have. Research can and does "fail" even with the best effort. Doing research on policies on Wikipedia is within Wikimedia Foundation's overarching programmatic goals to better the community to which donators donate to. There was a certain amount of funding allocated to the researchers, they tried to gain some useful information, they failed in the overall goal but found some interesting findings about internet communities which got published in a (what I assume) is a well respected journal. Sohom (talk) 02:55, 29 September 2026 (UTC)
No need to ping me. I have a watchlist and know how to use it.
Useful? Sure. $42,356 USD of the donor's contributions useful? Not so much. A lot of those donors are living in poverty and sacrifice to give because they were told that this was needed to keep Wikipedia free.
There are many, many researchers who have published papers on Wikipedia in well respected journals. I question why only a handful of insiders get funding for doing that from the WMF. --Guy Macon (talk) 03:06, 29 September 2026 (UTC)
seful? Sure. $42,356 USD of the donor's contributions useful?, that's how research works??? You provide a chunk of funding so that a group of researchers can try different methodologies and techniques and build prototypes to see if any work. If anything, 42K is fairly cheap in the research world for the length of time the project took (2022-2025) actually since if you think about it, a single grad student's yearly tuition and stipend in CS (being paid barely enough to sustain themselves, while also being one of the most funding rich areas) amounts to roughly that number.
I question why only a handful of insiders get funding for doing that from the WMF.. Guy Macon, I would suggest looking at the page for the dissemination of research funds which provides full transparency into who is allowed to put in proposals, how much money WMF is willing to give for research projects, the proposals submitted and rejected, the folks who decide who to fund (who are well respected researchers within the Wikimedia Research community). I don't think characterizing this as "insiders get funding" is a correct characterization. Sohom (talk) 03:22, 29 September 2026 (UTC)
As I have said many times, I think that everyone at the WMF -- from engineers to the people who decide who and what to to fund, are doing a great job at what they are trying to do. I have zero doubt that you are really looking hard at who you decide to pay to do research, and by "insiders" I don't mean "your buddies" or anything implying corruption or malfeasance. I believe you are like the fine people back in the 1960s who were managing the war in Vietnam. They did seriously great work deciding whether to fund more jeeps or more tanks, whether the jungle boots could be made better, etc. Thousands of good decisions were being made by dedicated individuals doing a great job, but never once considering or even being allowed to consider whether we should be fighting a war in Vietnam at all.
Now consider the entire world population of people who have published research on Wikipedia. All of them. They all get paid by someone, usually their university. What percentage get WMF grants? Do an honest estimate. One in a thousand? What differentiates the two groups? One group knows how to craft a proposal that will get them funding in the usual ways academics get funding. The other has learned how to work the system to get WMF funding. How many of each group get free travel and lodging to go to Paris and spend time with Wikimedia staff and Wikipedia editors? How many in each group know the names of multiple WMF employees? How can you call the tiny minority that get grants anything other than insiders? --Guy Macon (talk) 06:47, 29 September 2026 (UTC)
And again I ask, was this the sort of thing that the donation banners describe your contributions as funding? --Guy Macon (talk) 06:47, 29 September 2026 (UTC)
There's lots of things the WMF is doing badly, but I don't think this particular funding decision is one of them. The article seems to be of good quality to me, and seems in line with the research questions in the application. TietoTeekkari (talk) 07:56, 29 September 2026 (UTC)
And I fully agree, just as I agree that the military made some great decisions about funding jungle boots during the Vietnam war. They were great boots. I still have a pair and they look like new. And, just as I think that same military made those great boot decisions without even considering whether we should be there we should be fighting a war is Vietnam, I think the WMF did a fine job of picking which researcher to fund while never even considering whether we should be funding academic papers at all. And again I ask, was this the sort of thing that the donation banners describe your contributions as funding? Is there some special feature in Wikipedia's software that makes the preceding words invisible when I write them? --Guy Macon (talk) 13:50, 29 September 2026 (UTC)
Not Tieto, but the last time I donated to Wikipedia I recall the banner saying something about "supporting and defending open knowledge projects." I'm probably not getting the phrasing exactly right. This research seems very relevant to Wikipedia and how our internal community and governance systems operate, along with how community-based open knowledge projects operate more broadly. ThadeusOfNazereth(he/him)Talk to Me! 19:17, 29 September 2026 (UTC)
You mean this banner? The actual promise was "Please join the 2% of readers who give what they can to to help keep this valuable resource ad-free, up-to-date, and available for all". Nothing about supporting and defending open knowledge projects. The banner also talks about what you are doing when you visit Wikipedia, which I thought was a nice addition. Please note that something can be "very relevant to Wikipedia" without being what the donors were told their donations were funding.
You can see a bunch of fundraising banners here. I couldn't find any documentation as to which were shown when and to who. Perhaps someone else can find that information. --Guy Macon (talk) 23:45, 29 September 2026 (UTC)
Guy, it sounds to me that you want the WMF to support Wikimedia and open knowledge projects but to do no research into how to support those projects, no research into how effective support for those projects is, whether support would be better directed towards maintaining existing (governance) structures or implementing different (governance) structures? If so, why do you think that? If not, please try explaining what I'm getting wrong. Thryduulf (talk) 19:47, 29 September 2026 (UTC)
Not at all. The choice is not between "funding no research" and believing without evidence that this particular research actually ended up "maintaining/implementing governance structures". Can you name a single governance structure that was maintained or implemented by this research? Look at the results of this research again: The first two results are trivial and the third is just plain wrong.
In the banner at the donors -- many of whom live in poverty -- were not told that they were funding research, just as they were never told that they were funding trips to talk about Wikipedia in exotic vacation destinations. They were told that they were keeping Wikipedia ad-free, up-to-date, and available for all. I am fine with donors funding any research that has a reasonable chance of advancing those goals, but they should be told that some of their donations will be given to other individuals and organizations. --Guy Macon (talk) 23:45, 29 September 2026 (UTC)
Research does not have to be successful to have been valuable, and if you only fund research that produces the results that you want it to then that's not research. Please explain how funding people and projects that write and maintain the projects, write and maintain the sources we use, research how the project can be improved, research how best to support the projects, etc. are not "keeping Wikipedia ad-free, up-to-date and available for all" either directly or indirectly? Thryduulf (talk) 00:04, 30 September 2026 (UTC)
By those criteria I can't think of a single thing that the WMF spends money on that doesn't keep Wikipedia ad-free, up-to-date and available for all either directly or indirectly. I can't see any plausible way that not funding this sort of thing could possibly result in Wikipedia being ad supported, stop the volunteers from updating it, or make it unavailable, but you clearly do so I won't waste your time with further disagreement. --Guy Macon (talk) 00:18, 30 September 2026 (UTC)
Can you name a single governance structure that was maintained or implemented by this research? To this among other research appears to be part of a body of research into policies that eventually led to the establishment of the NPOV Working Group and the subsequent implementation of the global baseline NPOV policy. Sohom (talk) 00:27, 30 September 2026 (UTC)
Just to be clear: I think that Wikiresearch is in general a good thing, and funding some of this by WMF seems reasonable. The specifics of funding, methods, and transparency and ethics of the coordination of the research should, of course, be subject to transparent debate (apart from privacy issues). I'm not judging the validity of funding for this particular project. Boud (talk) 11:39, 30 September 2026 (UTC)
I found meta:Baseline NPOV policy (a baseline NPOV policy for the Wikipedias which do not yet have an NPOV policy) to be a fine document. The question is whether it is worth the $42,356.25 USD ($88.43 per word) it cost the donors.
I would be interested in how many Wikipedias did not yet have an NPOV policy when it was created and how many have adopted it. If the donor is paying for "governance structures implemented by this research" it would seem reasonable to ask how many actual governance structures were implemented, not just a web page that seems like it would be useful to someone doing that.
I also noticed that it is only in English and French. One would think that some of that $42,356.25 USD would have been spent on translating it to the languages of the Wikipedias which do not yet have an NPOV policy. I'm just saying. --Guy Macon (talk) 16:14, 30 September 2026 (UTC)
Couldn't small wikis just copy the NPOV policy from English, French or any other well-scrutinised Wikipedia, gratis, and alter any bits they deem inappropriate for their project? Certes (talk) 16:23, 30 September 2026 (UTC)
@Certes, I would suggest looking at Serbian, Bosnian Wikipedia situations where despite copying the policy text over over they've had multiple significant issues surrounding the enforcement of said policies. Similar issues exists to smaller extent on other projects as well. Even on the rather bare-bones baseline policy, smaller communities have pushed back on the baseline policy due to concerns over the fact that it often constrains smaller language wikis in multiple ways in terms of prioritizing spoken history vs colonial written sources or preferring accounts in local language sources over the broader international consensus on a topic. Sohom (talk) 16:38, 30 September 2026 (UTC)
Certes, the real problem in searching for worldwide solutions is that in my experience different language Wikis are effectively different planets with totally different climates. I sometimes look at the Italian, French, German and Spanish wikis, and their culture and customs are strikingly different, and range from those with a highly controlled system (eg German) to others with freewheeling on non-crucial topics. Their wiki cultures adre as different as the foods they eat. You can not give them a universal cookbook. Yesterday, all my dreams... (talk) 18:02, 30 September 2026 (UTC)
@Guy Macon The policy hasn't yet gone into effect. It is still in proposal phase. Also re cost, 42K (and more actually) spent on building policy to avoiding incidents where Wikimedia project's credibility is called into question is imo money fairly well spent. Sohom (talk) 16:40, 30 September 2026 (UTC)
That would indeed be money well spent if that's what the $42K bought. A bargain, I would say. The problem is that you have offered no examples where having One More Web Page On Meta actually avoided any incident where any Wikimedia project's credibility was called into question. Not even a plausible path where that might happen in the future. You seem to be saying that money spent on goals without any hint of a way to actually accomplish those goals is money well spent. I say that $88.43 per word is way above the going price for good intentions, which are currently so cheap that they pave roads with them. --Guy Macon (talk) 22:34, 30 September 2026 (UTC)
The problem is that you have offered no examples where having One More Web Page On Meta actually avoided any incident where any Wikimedia project's credibility was called into question - The m:CheckUser policy and the m:UCoC would be prominent examples of the a "page on meta fixes problems" effect. Sohom (talk) 00:21, 1 October 2026 (UTC)
Please accept my apologies in advance for saying this, but with phrasing like "Wikimedia Foundation's overarching programmatic goals to better the community" you could run for senate. The problem with their research results was similar. Too many words, too little substance. Sorry, but bluntness was needed here. Yesterday, all my dreams... (talk) 15:07, 30 September 2026 (UTC)
Foundation's overall goal of making the wiki community better is what I meant. Ignore the word programmatic, it's a reference to the way WMF and other non-profits calculates it's budget, (as programmatic expenses and non programmatic expenses). Sohom (talk) 16:28, 30 September 2026 (UTC)
Guy, I think $42,355.25 was wasted on the word salad they produced. The other $1 was useful, given that it made me laugh. Yesterday, all my dreams... (talk) 14:56, 30 September 2026 (UTC)
In this edit, Guy Macon wrote, The first two results are trivial and the third is just plain wrong. I think it would be good if Textaural, who is an experienced enwiki editor, could respond here. The peer-reviewed research paper is technically a WP:RS, so usable in enwiki articles, but peer review does not guarantee correctness.
I agree that the third key resultThe status of rules [on these 5 Wikipedias is] established largely by individual decisions and rarely through collective decision making is extremely dubious for at least enwiki and frwiki. The strings !vote and not vote seem to be completely absent from the published paper. In a nutshell: If I'm the individual to first write the enwiki policy that 1+1=2 is a fact and nobody contests that, it's not due to my dictatorial authority; it's due to the WP:!VOTE decision-making algorithm and the nature of 1+1=2 being widely considered as reasonable, without anybody needing to argue about it (leaving aside modern foundations of mathematics). The whole point of not holding a vote on my hypothetical new policy is that getting 10,000 votes (not !votes) with a likely result of 99.9% in favour would be a huge waste of time. @Textaural: How do you justify your extraordinary conclusion that Within the English-language rules, the authority of rules was based on the editorial authority of one user, who may have found support through limited deliberation without having studied the role of WP:!VOTEs in the establishment of enwiki rules? !VOTEs are a form consensus decision-making, which is a form of collective decision-making. The authority of rules is not based on the editorial authority of one user; it's based (often) on the ability of one user to successfully describe and summarise the current consensus or predict the likely consensus.
Textaural: do you have any evidence for this claim that you and your authors assert in the paper? The Methods section of your paper says nothing about how you quantify the unexpressed non-objections to enwiki rules (a possible method would be to obtain permission to do a survey of Wikipedians to see how much they agree with existing rules and whether or not they have tried objecting to rules they disagree with; but you don't seem to have done that). Boud (talk) 11:07, 30 September 2026 (UTC)
"Rules"!== policies to my understanding. Sohom (talk) 11:23, 30 September 2026 (UTC)
Fair enough, my understanding is that the paper discusses the individual rules inside the policies instead of the policy as a whole but I can see it being taken in both ways Sohom (talk) 14:04, 30 September 2026 (UTC)
I also noticed that the author uses https://artandfeminism.org/resources/research/unreliable-guidelines/ as a source. Artandfeminism.org appears to be funded by the WMF through WikiCed ( https://www.wikicred.org/). I can't find any record of how much the WMF gave artandfeminism.org to say "This research project identifies the ways that organizational values and processes around reliability and the reliable source guidelines are implicated in maintaining hierarchies and excluding marginalized knowledges and communities" and "Ultimately, the Reliable Source guidelines are an unreliable and incomplete guide to provide editors with a meaningful understanding of how to assess source reliability".
So what are we supposed to replace our reliable source guidelines with? "Triangulation". If anyone can understand what (cited by artandfeminism.org) is talking about please explain it to me. --Guy Macon (talk) 13:16, 30 September 2026 (UTC)
I don't disagree that Art+Feminism is funded to a certain extent by the Foundation, but last I checked, it wasn't through WikiCred? WikiCred organizes meetups in the West Coast and builds tools for media reliability on Wikipedia, Art+Feminism advocates for better coverage of topics related to gender, feminism and art (among other things). They were one of the advocates for a global UCoC and and have long advocated for changing our guidelines to be more inclusive towards marginalized communities and better enforcement of civility policies. I don't think there is a correlation between WMF funding Art+Feminism, Art+Feminism being cited as community criticism of the reliability guidelines and WikiCred organizing conferences. Sohom (talk) 16:25, 30 September 2026 (UTC)
Re: "last I checked, it wasn't through WikiCred?" you need to do a better job of checking. Look at Read the funding section. What we have here is an informal community of organizations united in the goal of writing proposals that will result in the WMF giving them grant money. If only the WMF would check to see if the goals in the proposal were actually met and, if not, find some other applicant to award the next round of grants to. --Guy Macon (talk) 23:00, 30 September 2026 (UTC)
To quote the paper, Unreliable Guidelines, a project of Reading Together: Reliability and Multilingual Global Communities, is an inaugural Art+Feminism research report partially funded by WikiCred, which supports research, software projects and Wikimedia events about information reliability and credibility. WikiCred and Art+Feminism are together funding the paper with At+Feminism being the primary sponsor and WikiCred being a partial sponsor. The Funding section in particular say The expertise of the main researchers was partially funded by WikiCred and Art+Feminism. i.e. that this project was a collaboration between AF and WikiCred. Nowhere does it say that the Art+Feminism is funded by WikiCred. Sohom (talk) 00:27, 1 October 2026 (UTC)
When I skimmed that paper yesterday, I also had several qualms with the methodology leading to those conclusions: off the top of my head, they ignored pages with a creation date before 2005; they only looked at edits which change the label (between essay, guideline, policy, etc.); and they only looked talk pages when explicitly mentioned in an edit summary.
To expound a little: if I'm reading it correctly, it would ignore (to list a few non-exhaustive examples), talk discussions not mentioned in the edit summary; discussions which affirm the status quo; changes which align content to community consensus without changing the "label" of a page; and implicit consensus where thousands of people have read a page and no one has found reason to change it. LittlePuppers (talk) 21:56, 30 September 2026 (UTC)
Well hello there! I've been meaning to respond for a while and just got the chance to do so and thanks for notifying me that this conversation was happening. I'm replying to @Boud here, but it is more of a general response to the discussion.
First, the goal as a researcher is to have your research read and discussed and if for anything else, I am grateful for that happening here. And I appreciate those of you who have defended my work (and "research" in general), but also Guy who is asking some hard questions that should be answered. I will break down my response to answer three questions: Why did it cost 42K to produce one paper? Is the research worth it to those who donate to Wikipedia? Are the results of this research interesting, valid, and valuable to the community? Textaural (talk) 13:13, 19 October 2026 (UTC)
Why did it cost 42K to produce one paper?
The most direct answer for this is that the university that manages the money also sets the pay scale for research time, and so that cost is actually somewhat outside of the individual grantee's hands. For some background, The WMF was interested in ensuring that the project I conducted covered as many possible language editions as possible because there is so little research done on policy itself, let alone Arabic, Spanish, and Dutch policies. To do this, I also needed to hire more researchers to do this work, and two of the researchers were multilingual (which did helped to limit the number of people involved). But to meet those requests by the WMF and to draw from the university's labour pool I did have to hire two post-docs.
In the end, a significant proportion of money went to paying all the researchers for their labour in accordance with university's own pay scale for research time. The secondary cost, but far far less than the cost of labour, was travel to one conference. We attended other conferences that we attended, but these were online conferences which incurred no extra cost for the grant. We also published with New Media & Society which is a top ranking journal in the field, but importantly, has an agreement with the university where the costs of publishing open access is covered by the university, and not individual researchers. This meant that the open access publishing cost (which can be about $4000-$5000 depending on the journal) was paid for by the university and itself, and not the WMF. As surprising as this may seem, in comparison to other research projects, my project was quite frugal.
That being said, the project was supposed to last only one year, I extended it for a second year because the research required it (but with no increase in grant money) and I ended up working many hours on it in my free time into a third year. So in fact, this project would have cost more if the entire research time was paid for. So while we are accustomed to thinking of knowledge as free here on Wikipedia, research itself in general is quite expensive.
So that is some of the details on the cost. Textaural (talk) 13:13, 19 October 2026 (UTC)
Is the research worth it to those who donate to Wikipedia?
I understand the reasoning of this kind of question, and I have two considerations of it. The first is that the WMF funds do not just come from the community. From the 2024–2025 Annual Report, 22 corporations (Google, Microsoft, Rockafeller, etc) and private citizens donated _at least_ over 50,000 each. A conservative estimate puts this group of major donors donating a minimum of 1.1 million. 47+ donated 15K-49K; another 108+ donated 5K-14K. This is missing sustaining donations and one-time donations. So a very conservative calculation is that at least 2.3 million of the donations in 2024-2025 came from organizations or wealthy individuals. What I'm trying to say is that Wikimedia's funding is diverse. So perhaps, if you are less keen on research like mine, the consolation prize is that we can consider that Google paid for it, not Wikipedians. But I obviously think this research does has value (see final question).
One thing I'd like to add is that the WMF continually highlights in the grant process that they expect researchers to connect with the community during the research phase. On this front I'll admit that I should have done better. But I was also a bit unsure at the time exactly how to go about it and where is the right place to notify Wikipedians that I was historically analyzing policy and what kind of feedback the research required. Despite my uncertainty, I should have tired. I am now more aware of how research can be communicated, and I at least know who to ask now when I start my next project. But any further advice would be welcome. Textaural (talk) 13:13, 19 October 2026 (UTC)
Are the results of this research interesting, valid, and valuable to the community?
First, this research is historical in nature, looking at how policies first emerged and gained their authoritative status in the form of policy templates, and so the immediate outcome for the community is to gain an additional view on how the encyclopedia developed. Second, one critique was that some of the results were trivial, and one was wrong. The two "trivial" conclusions are (at least from my perspective) descriptive conclusions, they are facts. Making facts that are rooted in empirical evidence is difficult, time-consuming and painstaking work, something that all Wikipedians are aware of. So now there is a reliable source for these facts.
It was also pointed out that this research was framed on its meta page as wanting to find gaps in the policies. On this front, what we identified is that a the explicit authority of policies (as it is advertised in the policy template at the top of the page: "This is a policy") was itself often not created out of a consensus process, but was created through the decisions of a very few users. In the language of gaps, I see our research as indicating the ways that some things that we think are made through consensus on Wikipedia, are assumed to be, when in fact a close inspection shows this not to be the case. As such, our article makes a small but substantial argument: that here, in the specific cases of how early policies were tagged as policy, guidelines, etc, was not itself derived through a process of consensus. This does not mean other parts of a rule were not created through consensus, just this specific part that tells everyone on Wikipedia which wikipages are policies and which ones are not.
The evidence was based on looking at 15 rule pages, and examined their development (usually the late 2000s; early 2010s), tracking who said and did what around the times when the status of a policy changed. We have a clear We found that some fundamental policies were given the authority of a "policy" adding the policy template, rather than a coherent and explicit deliberation of many users. As such, I argue that this does not qualify as consensus as broadly imagined. Indeed, trying to understand what consensus is and how it manifests on Wikipedia is an interesting question that is a focus of my research (here and here and here) and this paper extends these ideas.
So why does it matter? There are cases where the process where a rule gains its authority as a policy is not in keeping with the ethos of consensus. The application of a template of "This is a policy" is self-reinforcing. In other words, the article asks that we actual examine how the authority of these policies were designated in the first place, rather than taking it for granted: something that I think is important to consider for all policies. And I hope leads to making Wikipedia get even closer to its ideals.
And if you are more curious about the argument, I encourage you to read it, and if you have questions about the empirical side of the argument, the dataset is also available. Textaural (talk) 13:14, 19 October 2026 (UTC)
Hi Textaural, thanks for the response. I'm curious how you would respond to my initial conclusions from skimming that paper: basically, that (as far as I could tell from reading your methodology) only looking at changes specifically to the page and those directly referenced in edit summaries ignores many forms of consensus-building. For example, a talk page discussion that was not mentioned in an edit summary; community discussion at some other venue (e.g. WP:VPP); a discussion which affirms the current status (thus strengthening consensus but not leaving anything in the page history); etc.
And regardless, I think it's also worth considering how changes to a policy over time bring it more in line with consensus; in short, perhaps back in the early 2000s (well, late 2000s, as policies from the early 2000s were excluded from your study) there were sometimes these nigh-unilateral status changes, but (and I'm not trying to put words in your mouth) I don't see a compelling argument that, after hundreds of discussions about and tweaks to these policies and guidelines, and thousands of people referring to and using them, they don't reflect something near to consensus now.
(Sorry, I know that's not particularly eloquent prose, but hopefully it's comprehensible. I'm just trying to understand your research better and what it does and does not cover.) LittlePuppers (talk) 21:11, 19 October 2026 (UTC)
On the point: The two "trivial" conclusions are (at least from [Textaural's] perspective) descriptive conclusions, they are [factual claims]. [Rooting factual claims] in empirical evidence [for or against them] is difficult, time-consuming and painstaking work, something that all Wikipedians are aware of. So now there is a reliable source for these facts, I fully agree (though I've reworded a bit more carefully from a WP:WIKILAWYERING POV). Boud (talk) 12:32, 22 October 2026 (UTC)
@Textaural: Glad that you've responded. However, you have not responded in plain language to the basic concern about your third claimed result: that you have not measured the full participation in the rule making used in the standard Wikipedia consensus decision-making algorithm and you have nevertheless made strong claims that the rule making was highly non-participatory, i.e. your published claim is not supported by your evidence, and you don't yet seem to have acknowledged that. Per Rhododendrites' suggestion below, I've started a section on metawiki on the talk page describing your article. I propose that people interested continue the discussion over there. I already pinged two people over at meta, I'm not sure if Sohom Datta wants to follow that discussion too. And, of course, there are the non-commenting implicit participants in this discussion who are leaving no trace in the wikirecord: those who feel that the things already stated are sufficient and feel that their overt participation would make the thread more messy rather than clearer. I cannot ping those implicit participants. Boud (talk) 13:34, 22 October 2026 (UTC)
Can I suggest separating, to the extent possible, the funding question from an evaluation of the paper? The WMF does not read the outcome of a project before funding the project, of course, so really it's a question of "should the WMF invest in research about Wikipedia governance" not "should the WMF invest in this paper". Yes, "was this worth it" is a fine question to ask, and one that the WMF answers internally, too, but any evaluation of the funding question should be based not on "I found one I'm skeptical of" but on a full accounting of related projects. I haven't engaged deeply with this paper yet (open in a tab in my "to read" window for some time, sadly), but the project sounds worth doing to me. We have precious few studies that examine Wikipedia governance anywhere but the English Wikipedia, and a direct comparison between several language editions is very potentially valuable. And NM&S is easily one of the top journals for non-computational Wikipedia research these days. That doesn't mean everything it publishes is perfect, but it has a high rejection rate, intense peer review process, and deep bench of Wiki-knowledgeable reviewers. That said, as with any Wikipedia research, it's also valuable when volunteers evaluate the content and correct the record, if appropriate. A quick search through the signpost archives doesn't turn up a match, so maybe it's a good fit for the next Research Report. —Rhododendritestalk \\ 16:16, 30 September 2026 (UTC)
I couldn't find an easy way to view multiple grants to the same researcher, but The WMF does read the outcome of a project before funding the next project by the same researcher. --Guy Macon (talk) 10:28, 6 October 2026 (UTC)
On a couple of occasions Guy Macon has said A lot of those donors are living in poverty and sacrifice to give because they were told that this was needed to keep Wikipedia free. I wonder what evidence supports this claim. I find it far fetched. Johnjbarton (talk) 15:33, 22 October 2026 (UTC)
I will be happy to support my claims with citations to reliable sources, but I need to know exactly what you are objecting to.
Are you claiming that the WMF doesn't send banner adds that get read by people living in poverty in Appalachia, India, and western Africa?
Are you claiming that the WMF doesn't clam in those banner ads that donations are needed keep Wikipedia free?
Are you claiming that the banner ads are totally ineffective and do not result in donations?
Are you claiming that for some reason only people above the poverty line respond to banner ads by donating?
Something else?
Please let me know exactly what you are disputing so I can post evidence to support my claims. --Guy Macon (talk) 16:15, 22 October 2026 (UTC)
I am challenging you to support your claim that a significant number of donors suffer hardship because of WMF actions. I do not think you polled donors living below the poverty line and determined that they were deceived. I do not think you represent a harmed class. Your critique of 0.0002% of the budget is fine, because an open source project should be open to criticism. But you should speak for others. Johnjbarton (talk) 16:43, 22 October 2026 (UTC)
Got it. You agree that the WMF sends banner adds that get read by people living in poverty, that those banner ads say that donations are needed keep Wikipedia free, that people respond by donating, and that some of those people are living in poverty. Your only objection is that the WMF (the only source that has access to that information) hasn't published data on donations by people living in poverty, and you refuse to believe that they exist if you can't count them. Thanks for clarifying your objection. --Guy Macon (talk) 17:15, 22 October 2026 (UTC)
Guy, it is not in dispute what the banners say, or that people living in poverty see those banners. What is being asked for is evidence for your claims that
People living in poverty donate in response to those banners
People suffer hardship because they donate in response to those banners
You say in your most recent comment that evidence for those claims does not exist, if so then you need to withdraw those claims and stop making them. If that evidence does exist, then you need to present that evidence. You cannot continue to cast aspersions on the WMF without evidence. Thryduulf (talk) 17:33, 22 October 2026 (UTC)
The burden of proof is on anyone who makes the extraordinary claims that you can take money from people living in poverty without affecting them or that poor people don't respond to WMF banners. --Guy Macon (talk) 17:48, 22 October 2026 (UTC)
You are the one making the extraordinary claims that the WMF are taking money from people living in poverty and that people are donating so much to the WMF that they are suffering hardship as a result. You have still presented no evidence for either of those claims. Thryduulf (talk) 18:39, 22 October 2026 (UTC)
That's not how it works. None of my claims are extraordinary. Yours are so extraordinary and outlandish that I frankly refuse to believe that you actually think that poor people don't respond to WMF banner adds or that poor people are not harmed by making them poorer. Who made the claim is irrelevant. Whether I make a claim that ghosts exist or that plants do calculus or whether you make the claim that they don't, the burden is on the person making the extraordinary claim, not on whoever made the claim first. -Guy Macon (talk) 23:01, 22 October 2026 (UTC)
Guy Macon, you said I will be happy to support my claims with citations to reliable sources... Please let me know exactly what you are disputing so I can post evidence to support my claims. We would like sources showing that A lot of those donors are living in poverty. LittlePuppers (talk) 23:17, 22 October 2026 (UTC)
5.46% or Wikimedia foundation ads get clicked on. 3.77% result in donations.
Families living in deep poverty face profound material, social, and emotional hardships. Households in deep poverty suffer from food shortages, unemployment, unstable housing, inadequate medical care, electrical shutoffs, and isolation. All US states have at least 5% of their children living deep poverty, including nearly one in five Black children under the age of five (Deep poverty is defined as living in a household with total cash income that is below 50% of the poverty threshold. It is a higher income level that the extreme poverty levels discussed above.)
I would also like to see your reliable sources that show:
People living in poverty donate to the WMF because of the WMF's fundraising banners
People suffer hardship because they donate to the WMF because of the fundraising banners
Those are claims that you made. You offered to support claims you make with reliable sources. Please do so. The burden is not on me to support claims that I am not making. Thryduulf (talk) 23:52, 22 October 2026 (UTC)
That's not how the burden of proof works. The burden in on the person making extraordinary claims, not on whoever spoke first. If I say that the Loch Ness monster doesn't exist and you reply that it does, the burden of proof is still on you to prove it exists because your is the extraordinary claim. --Guy Macon (talk) 00:26, 23 October 2026 (UTC)
Those are claims you made. Those are extraordinary claims. Therefore the burden of proof is on you. I am not making any claims, extraordinary or otherwise, I'm simply asking you to provide the evidence that backs up the claims that you are making, claims which you have claimed are supported by reliable sources. Thryduulf (talk) 00:48, 23 October 2026 (UTC)
None of those sources support any of the claims that you are making. They do support claims that nobody is disputing, specifically:
The WMF run ads in those territories
Some people who see ads click on them, and some of those people donate
Some people who live in those territories live in (extreme) poverty
Deep poverty causes harm to people who live it
Remember that correlation does not imply causation, and you haven't even shown correlation here. Thryduulf (talk) 00:56, 23 October 2026 (UTC)
This is not something that will be resolved by citations. It's a rhetorical move -- invoke a hypothetical sympathetic donor to delegitimize whatever the criticized-expense-of-the-day happens to be. In my opinion, the "people donate their hard-earned money because they think Wikipedia will die without it" argument makes some sense when criticizing the intensity of banner appeals, but just sounds condescending when trying to litigate specific expenses. At the end of the day you can accept it or ignore it, but it's not a citation issue. —Rhododendritestalk \\ 17:34, 22 October 2026 (UTC)
Good point. If the banner ads said something like "your donations go towards all the good things Wikipedia does" my entire argument would collapse and I would withdraw it. It is the combination of claiming that without your donations Wikipedia will no longer be free and the spending of those donations on things that have nothing to do with Wikipedia remaining free that I object to. Remove either leg and the argument falls over. --Guy Macon (talk) 17:48, 22 October 2026 (UTC)
Ok so you just represent Guy Macon. I think your argument makes sense in these terms, even if I don't agree with your conclusion.
In my opinion, the research effort Slow Editing Towards Equity was a high leverage investment in keeping Wikipedia "free". High-leverage because this amount of money is very small; investment because it was risky. It resulted in a published paper, above average results for that small investment. It engaged with scholars which may help further scholarly work on the structure of Wikipedia and its effectiveness. This kind of work might even be more important than paying electric bills for servers: Wikipedia has been challenged as unfair by both progressive and regressive ideologs so some exploration in to the effectiveness of policy structure makes sense. Being taking over by ideologs seems to me one o greatest risks to Wikipedia. Since "some" is in this case "almost trivial" this investment seems ok to me. Johnjbarton (talk) 18:29, 22 October 2026 (UTC)
I am writing to you today with an update on the planned changes to the Board elections process. The Board has been receiving feedback on its original elections process proposal since July. Thank you to the many people who participated onwiki, in person, or in direct conversation with Trustees. The feedback was extremely helpful.
Based on this feedback, the Governance Committee has decided that the eligibility criteria approach (as originally proposed) is not a good fit. Instead, we have developed two potential approaches we can utilise in the future. We are asking for your feedback again to inform our decision about which approach to use, starting with the 2027 selection process. Our goal is to have a process that is predictable and that does not require annual updates, although we recognise there may need to be minor adjustments in the future depending on facts and circumstances and lessons learned from 2027.
From a Board governance perspective, the fundamental requirement is that every trustee strengthens the Board and benefits the Foundation through the experience they bring. The Board oversees a community- and technology-focused international nonprofit organization with over 600 staff members across dozens of countries and an annual budget of almost USD$250 million. Every trustee must be able to operate, support and contribute in that environment. In addition, they:
must be able to work well with others;
must be able to make informed decisions based on an assessment of the best interests of the Foundation;
must be able to ask insightful questions;
must be willing and able to communicate decisions to the community and in other public spaces; and
they must have the confidence necessary to contribute their opinions and perspectives.
All trustees must also be able to commit to the confidentiality agreement of the Wikimedia Foundation in addition to exercising sound judgment and discretion, as well as managing any potential conflict of interest, both within and outside the Wikimedia Movement. The question is how to design an election process that ensures that every candidate on the final ballot meets that bar while still being a meaningful election where Wikimedians are the ones selecting the winning candidates.
Regarding "While the Board cannot forego its vetting process and its authority to remove candidates from the final list, we can make the process clearer", one of the major concerns among the volunteers has been the possibility of a future board making a decision that is so unpopular that is sparks open revolt among the volunteers, followed by the same board removing any candidate that does not support the decision.
While I have no doubt that the current board is pure and good, I do not have the same confidence in all possible future boards. By allowing the board to select itself you are preventing any any future reform movement from firing the board without the board's permission, no matter how bad that board is. This appears to be a clear conflict of interest.
Honestly? If the board isn't willing to take a far more liberal approach to board elections, then they should just be honest about it and drop the façade that the community has a meaningful voice on the board. CoffeeCrumbs (talk) 01:28, 11 October 2026 (UTC)
First choice recommendation: I recommend that someone who has no COI look at potential candidates and disqualify those that need disqualifying. Form a new group that does just that, hire an outside consultant, anything other than giving current board members the power to decide who can and cannot be elected to the board. Second choice recommendation: Stop pretending that this is an election. Just be honest and let the board select new board members without the sham election.
If you are serious about this being a fair election, whoever does the vetting should commit to disqualifying candidates without regard to whether they are likely to reverse any decisions of the current board, and should not be in a position to benefit from future board decisions.
Guy's suggestions are about what I think. Either have an outside consultant screen for set, objective standards or just drop the whole pretense. We're adults here; this isn't a grade school student council election where kids running promise more pizza days and homework bans. If you're not going to let the Wikipedia community have the power to elect people who can change the course of the WMF against what the board might currently want on some issues, then the elections are just Politburo "elections." CoffeeCrumbs (talk) 19:57, 14 October 2026 (UTC)
I agree with Guy. Elections where the board can arbitrarily reject candidates are not real elections, they just give the resemblance of community representation without giving any power to the community (which is worse than no elections at all). If screening is so important (why? Is the community choice not enough?), it should be done by a third party that is not influenced in any way by the board or the WMF Ita140188 (talk) 09:46, 15 October 2026 (UTC)
I also agree. I'm seeing an accelerating trend, of WMF leadership looking upon experienced members of the editing community as being something other than what the WMF movement is about. Kiss up, kick down leads to organizational obsolescence. --Tryptofish (talk) 23:58, 15 October 2026 (UTC)
RE: The requirements for a board member
The community being 4th, lumped in with the public as a whole, and only presented as something to be communicated to (rather than worked with) is deeply concerning and suggests the board failed to learn from all the happenings earlier this year. MetalBreaksAndBends (One for all) 14:15, 15 October 2026 (UTC)
It's deeply concerning but I think it's a difference of opinion rather than a lack of understanding. Wikipedia editors want a say in the governance of Wikipedia; the WMF wants to prevent that. Certes (talk) 15:16, 15 October 2026 (UTC)
Which seems like a relatively recent development to me. I don't remember the Trustees being like that when I first started editing in 2018, but maybe I wasn't paying attention. Levivich (talk) 18:09, 15 October 2026 (UTC)
"All organizations eventually come to be run by a leadership class... Far from being servants of the masses, this leadership class, rather than the organization's membership, will inevitably grow to dominate the organization's power structures... These mechanisms can be used to strongly influence the outcome of any decisions made 'democratically' by members."
We really need to take away the board's self-created total immunity to any reform now, while the volunteers still pretty much agree with the direction the WMF is going. If we wait until some future where the volunteers have formed a angry mob with torches and pitchforks vowing to take down a future board. the likely result will be replacing one bad set of all-powerful oligarchs with another slightly less bad set of all-powerful oligarchs. --Guy Macon (talk) 00:49, 16 October 2026 (UTC)
Well, looking at the stats for the last election, I think the pro-wwu block will be at least a significant minority in the next election. I, for one, will be voting for the most-wwu aligned candidates who are at least mildly competent, and will likely vote replicating whatever the most popular wwu-aligned guide is, if there is one. MetalBreaksAndBends (One for all) 02:06, 16 October 2026 (UTC)
It's worth keeping in mind that unionization of WMF employees is only one part of what is going on here. There are broader issues of whether or not the Board is willing to listen to what the editing community is saying, in many different aspects of how the WMF works. --Tryptofish (talk) 23:25, 16 October 2026 (UTC)
While the union has received a lot of attention lately, there are many other areas where both WMF management and the board appear to be highly motivated to never let the community have a say. As an example, I have repeatedly asked a Frequently Unanswered Question (F.U.Q!) that I am convinced will disqualify any candidate that shows a willingness to ask it: Pick a Wikimania. Any Wikimania. Tell us what it cost our donors and who received the money (as far as possible without naming any individual or violating anyone's privacy). --Guy Macon (talk) 02:24, 17 October 2026 (UTC)
I am aware that there are far far more issue with the WMF than just the handling of WWU. But support for the WWU is highly correlative with other good positions, so asking "What do you think the WMF did wrong with regards to WWU and the community?" and "How will you prevent similar breaches of volunteer trust in the future?" both show a person's stance on more than just WWU while also giving people who's first instance of WMF betrayal was comtech and/or WWU a clear guide on who's good and bad. MetalBreaksAndBends (One for all) 03:17, 17 October 2026 (UTC)
Reminder: meta:FUQ is ready for further edits. Currently two unanswered questions + one question answered within seven weeks. Boud (talk) 16:51, 22 October 2026 (UTC)
"The question is how to design an election process that ensures that every candidate on the final ballot meets that bar while still being a meaningful election where Wikimedians are the ones selecting the winning candidates." A clearer admission that the Foundation does not trust or respect the ability of the community to make good judgements would be hard to imagine. DuncanHill (talk) 23:29, 16 October 2026 (UTC)
What concerns me most is that the criteria for disqualification appears to be entirely arbitrary. I’d understand if they had specific, well deliberated red lines based on obvious community interests that they point out and hold to, but they’ve left it instead as an indeterminate line in the sand that they can seemingly redraw whenever they want depending on whatever their concern at any given moment is. It’s quite easy to justify that with the notion of “well we don’t know what we’re going to come up against”, but the fact that they won’t give the boogieman a face or even a facade as a good faith gesture to the community in advance (to allow time for potential nominees to consider input by the community writ large and self-select in the interest of putting forth the most undisqualifiable candidate who nonetheless shares their underlying values), is what irks me most heavily.
Democracy ultimately starts to crumble when leaders monopolize the authority to determine what (or who) is right or wrong, and what’s ultimately an acceptable question for the electorate to get to answer. If they’re implying here that the community they’re responsible for governing can’t be trusted to act in its own interest and not elect a fascist, then we really should just close up shop right now, they’ve clearly already failed spectacularly in their mission.
The Wikimedia Hackathon, the yearly software engineering conference, may stop being a global conference
I can't say I'm very happy about this proposal: mw:Wikimedia Hackathon/Community Proposal 2026. This is a conference for Wikimedia software developers that I attend yearly, and that I consider to have an extremely successful format. The above proposal appears to want to take the money spent on this conference and basically kill it off to spend it on smaller regional conferences, except for every third year.
I'm not sure this is the correct place to post this or if it will resonate with people here. But this is something in the pipeline that is frustrating me. I wish WMF would leave stuff that's working alone and not make big changes to it.
I really hope this doesn't become a wishlist situation, where we have to put up with a poor format for a couple years, then finally there is a big backlash to get it changed back. I'd rather they just not make the questionable changes in the first place.
Thanks for listening. –Novem Linguae (talk) 06:09, 18 October 2026 (UTC)
"Our goal is to better understand whether concentrating our resources on one global event held in the same region each year creates barriers to participation or limits our ability to develop technical contributor communities in other parts of the world." There seem much easier ways to trial this than an immediate three-year experiment. For example, there are already regional conferences, trial a hackathon at one or two of those. Much less money spent for the same experiment without immediately affecting the current process. CMD (talk) 10:36, 18 October 2026 (UTC)
@Novem Linguae - Thank you for the feedback and I appreciate you making sure that the entire community has an opportunity to comment. To be clear, the goal isn't to mess with something that is working, but to provide an opportunity to discuss something that others in the community have raised questions about.
So far, there's been lots of really valuable feedback on what works and doesn't with hackathons, as well as alternatives to the one provided in the proposal (like @CMD's proposal above). To ensure that others have an opportunity to see your comments and engage with them, I'd encourage you to comment on the proposal's Talk Page. ~2026-57722-47 (talk) 19:04, 29 October 2026 (UTC)
My apologies! Just realized I wasn't logged in when I replied, this is from me (@BPiovesan-WMF) BPiovesan-WMF (talk) 19:05, 29 October 2026 (UTC)
Thank you very much to everyone who has contributed with feedback on wiki, at the recent conferences in-person, and on online meetings. Special thanks to those who acted as facilitators gathering and consolidating feedback from specific communities and organizations. This quantity, quality, and diversity of feedback helps us to make improvements in the proposal.
Moving forward, we plan to identify specific questions requiring further discussion and collaboration. We are also thinking of using additional ways to gather feedback and collaborate, to allow wider and also deeper participation beyond talk page discussions and sessions at events. More about all this soon.
In the meantime, we are still open to feedback at the upcoming regional conferences and online calls, as well as on meta, especially from those who haven’t got a chance to share their opinion yet. We will continue listening and integrating feedback as we go. --KVaidla (WMF) (talk) 11:24, 20 October 2026 (UTC)
Digital Security During Election Time: A Workshop with Freedom of the Press Foundation
Election time can be a difficult moment for your digital safety. Political issues take center stage, emotions run high, and online harassment, from unwanted messages to threats and doxing, becomes an easy way to target Wikimedians.
Ahead of the 2026 United States elections, the Human Rights Team, with the kind support of the Freedom of the Press Foundation, is hosting a 90-minute session for Wikimedians to learn about and connect practical steps to protect your privacy and stay safe while contributing to Wikimedia projects and participating in movement activities.
All experience levels welcome. Bring your questions!
New post at the WMF Fundraising Hub - October update
Hi everyone,
A new post is available over at the Fundraising Hub. Have a look what is new in our October update. Best, JBrungs (WMF) (talk) 08:22, 26 October 2026 (UTC)
New features for quickly finding bad-faith content
We (the Wikimedia Foundation Product Safety and Integrity team) have been working with volunteers for the last several months on new ways to automatically detect different kinds of bad-faith edits, which are then shown to volunteers to take action on, through a new special page called AbuseReview.
We have focused on two kinds: personal information that likely needs to be suppressed, and vandalism that likely needs to be reverted.
We figured the community here would appreciate some insight into the data we’re seeing and how these features work, including how it interacts with ClueBot NG and existing patrolling efforts. We have a project page that we’ve been updating along the way.
Detecting personal information
For this feature, oversighters are shown likely disclosures of non-public personal information, which typically should be suppressed or revision-deleted according to the oversight policy.
As volunteers described here a couple months ago, it took us working together through several iterations and a lot of manual labeling to develop an accurate classifier. Fancy AI stuff can only get you so far - we would not have been able to make something good enough without hard human work and expertise.
Since deploying this feature, the amount of personal information that is getting caught and removed on English Wikipedia by volunteers has roughly doubled. Oversighters have told us the accuracy rate is consistently better than the human reports they are used to receiving.
Personal data flagged on the Special:AbuseReview page and suppressed
This is built using an AI-powered classifier that runs on top of a language model. After evaluating multiple models, we are using CoPE-B, an open-weight model that is trained specifically for trust and safety purposes, and is maintained by the team at zentropi.ai. We are self-hosting this model, so the live edit analysis is all happening inside our infrastructure.
To use the classifier, we provide the model a plain language “prompt” that describes the specific factors to include and exclude. This prompt was written to match community oversight policies, and has been refined over time based on feedback from volunteers and observed performance.
If you are interested in how CoPE-B works, the creators have published a paper and talk about it on their blog. As a rapid classifier that emits yes/no decisions with confidence scores, CoPE-B bears a strong resemblance to what have more recently been coined “decision models”, like Jev and Clef. In fact, Zentropi recently published a new variant of CoPE-B that is more directly compatible with the “decision model” framework, and which we expect to evaluate soon.
Detecting vandalism
For this feature, volunteers are shown likely vandalism that should typically be reverted. This uses the same model (CoPE-B) as personal information, with a vandalism-focused prompt.
This has been running on English Wikipedia for about a month now, but as a limited alpha test accessible only to a group of volunteers involved in patrolling who raised their hand to help us test the feature. Similar to our development of the classifier for personal information, many of these volunteers also put in the time to manually review many edits to help give us solid data and feedback to work with.
We know there’s already a lot of energy on English Wikipedia when it comes to tackling vandalism, in human and bot form. We consulted with patrollers and with the ClueBot NG team, and we’ve been clear that we don’t intend to displace existing efforts. To avoid creating disruption as we introduce this tool, we are currently defaulting to a delay of a few minutes before surfacing likely vandalism, to let ClueBot NG and others “go first”.
By doing this, we’ve seen that there is a steady stream of vandalism that is slipping through the existing net of bots and humans, and that this classifier can help catch it. We’ve seen less than 1% of flagged edits reported as false positives, and we see a measurable speed-up in how quickly vandalism is getting reverted on English Wikipedia – especially in the longer tail that otherwise might have stayed online for many hours or days.
Time to mitigate vandalism flagged on the Special:AbuseReview page
What’s next
Given the above, we’re now ready to move the vandalism feature out of testing and open it more widely. To start, we have opened Special:AbuseReview to all rollbackers and admins on English Wikipedia. If this community thinks that the feature should be gated on different rights, it isn’t meant to be set in stone, but we do think it is important that the judgments being made within Abuse Review represent experienced patrollers.
Overall, it really seems to us that this new generation of classifiers is a huge quality improvement over what we and volunteers are used to in this space. We are internally working next on a classifier focused on link spam, and early results are already promising.
Finally – while we started with English Wikipedia, we have since worked with oversighters and others on other large Wikipedias to deploy this feature there too, and it seems to naturally translate pretty well. We are open to bringing this to other wikis that are interested.
We are interested in your thoughts – and of course, we deeply appreciate all of the volunteer collaboration on this project so far. EMill-WMF (talk) 16:30, 27 October 2026 (UTC)
I have used the AbuseReview tool for private information extensively, and it works great for quickly identifying likely PII exposure for quick suppression. Often, I'm reverting the edit before anyone is likely to have seen it, so we're likely suppressing before any exposure, as opposed to the old model either finding it while patrolling or someone seeing it and reporting. I've also used the vandalism detection mode, which has also been effective at surfacing edits that may have slipped past recent changes patrollers and Cluebot. Count this as a strong endorsement of both of these tools from me. ScottishFinnishRadish (talk) 17:54, 27 October 2026 (UTC)
I also want to say that I hope that we'll see a way for editors to report issues for revdel and oversight directly into the AbuseReview tool so there is a private on-wiki way to make these reports, which would be a huge upgrade over the current status quo. ScottishFinnishRadish (talk) 11:35, 28 October 2026 (UTC)
+1 to a private on-wiki "button" to request revdel and oversight Netstars22(talk to me!) 18:32, 30 October 2026 (UTC)
This seems like a good idea. I've gone ahead and created phab:T443112 to move the idea along to the next step. –Novem Linguae (talk) 10:22, 31 October 2026 (UTC)
Also a very strong endorse from me. I was honestly shocked to see how much blatantly obvious vandalism gets past recent changes patrol, since my newbie experience of attempting to help out with that was that all the vandalism I found was reverted faster than I could get to it. As for the suppressible information... well, I knew it was that bad already, and I think we're surely still missing out on quite a lot. But this has been a huge help in surfacing things that should have been suppressed, but were not reported. In solidarity, asilvering (talk) 19:58, 27 October 2026 (UTC)
I don't have much to say except that I love this. Keep up the good work.
Is there any chance that we will be able to run this on historical edits/pages, so that we can chip down on long term vandalism? EatingCarBatteries(contribs|talk) 20:08, 27 October 2026 (UTC)
I had a short conversation about this with @EMill-WMF a week or so back after becoming aware of potentially libellous material that had been present in a BLP article for several months (since before AbuseReview went live). Based on that conversation, my understanding is that, at least for personal information, something like this is seen as desirable but the practical implementation has not yet been determined. We agreed that simply scanning the whole database and dumping any hits into AbuseReview would overwhelm the system, and this would be even more the case with vandalism (instances of which are more numerous). Several ideas have been suggested but the priority has been to get the live version production-ready first. Thryduulf (talk) 21:58, 27 October 2026 (UTC)
It's great to hear that's being considered. I hope that this does come to fruition, as well as for different purposes like promotional text.
If the system prompt being used is public, I'd imagine someone can repurpose it to run it on their machine on an enwiki dump. But it would take a metric ton of compute to scan on one of those all-revision dumps. EatingCarBatteries(contribs|talk) 07:04, 28 October 2026 (UTC)
I share my colleagues' enthusiasm for this. Finding PII in real time has been a consistent challenge, and the tool for that has made a measurable improvement. Our core purpose here is building an encyclopedia written by humans. Handling vandalism and private information is a necessary task to that enterprise, but it's an unpleasant janitorial task that sucks up editor time. I deeply appreciate the fact that PSI developed a means to automate some of this effort, and also that they worked with volunteers to bring in a level of quality control we are happy with. Vanamonde93 (talk) 20:13, 27 October 2026 (UTC)
It's been a few years since I've regularly done much anti-vandalism work, but from a brief look I really like this tool.
One comment: can we get a button to update the list, rather than having to refresh the page? (Or am I missing something?) LittlePuppers (talk) 21:00, 27 October 2026 (UTC)
You're not missing something, the product is.:) We are in fact working to deploy a "live refresh" mode soon, hopefully next week. EMill-WMF (talk) 21:07, 27 October 2026 (UTC)
I've been using the personal information side of AbuseReview and I can't endorse it highly enough. It's catching the additional of personal information before even new page patrollers can, so we (Oversighters) can suppress it before even they see it, reducing the exposure to sometimes very sensitive information. Thryduulf (talk) 22:01, 27 October 2026 (UTC)
Out of curiosity, what kind of personal information are people trying to add? Is this a matter of people trying to dox another person, or something a newer editor may think is innocent? EatingCarBatteries(contribs|talk) 06:29, 28 October 2026 (UTC)
@EatingCarBatteries Speaking from my personal experience (both as a former child on the internet, and the stuff I've sent into OS): children like posting stuff like which elementary school they go to, what street they live on, their phone number/email address, their full names, ect. This is obviously, not a good idea, but children do not always have a good sense of internet safety. GreenLipstickLesbian💌🧸 07:20, 28 October 2026 (UTC)
@EatingCarBatteries all of the above. People posting their own information is the most common, especially children as noted by GLL, but also apparent adults posting their contact details (email, phone number, sometimes street address) and occasionally other personally identifiable information. Posting the details of others also happens, most often this is in good faith, e.g. children including details of their family members alongside themselves or people adding too much information to biographies, but doxxing does happen. There are also cases that might be self-promotion/spam, might be innocent oversharing or might be doxxing but we have insufficient knowledge to tell (e.g. a pseudonymous editor sharing a phone number for Joe Bloggs might be Joe themselves or might be someone attempting to doxx Joe). Thryduulf (talk) 11:28, 28 October 2026 (UTC)
And to add to both of those, there are also people who think that the talk pages are for contacting an article subject. Those people tend to leave contact information. On pages dedicated to government agencies, they tend to leave... much more than just contact information. In solidarity, asilvering (talk) 17:16, 28 October 2026 (UTC)
+1 to above comments - 9 times out of 10 the PII is fairly "typical" (in that in the era of data breaches and data brokers it's probably already out there if you look) so names, email addresses, postal addresses and so on. Once or twice I've seen ID numbers (which in that case is clearly being done with malicious intent). Netstars22(talk to me!) 18:48, 30 October 2026 (UTC)
Hello! I'm not an administrator, but I do enjoy reverting vandalism. Is there some way with which I can apply to access the vandalism detections without running for admin? I'm not interested in seeing any of the personal info stuff, obviously. GrinningIodize (you just lost the game) (talk) 17:21, 28 October 2026 (UTC)
Ooh, this looks interesting and promising - nice work y'all. One interface request I do have: in addition to live refresh, would it be possible to adjust the "rollback" button to do it in a new tab or window, rather than in the same window? Netstars22(talk to me!) 18:31, 30 October 2026 (UTC)
This appears to be an industrialized doxxing threat from the Anti Defamation League. Is there a way to formally ask the WMF to request clarification on what exactly they are doing?
What exactly is the concern here? They are allowed to do this. There's nothing illegal, People do the same thing manually when gathering evidence for SPI or ArbCom. The tools that let people track editors are built into mediawiki. It's the user contributions and page history buttons. Packaging that information up into something that highlights shared pages, or related contributions, or similar content of edits is not objectionable and in fact would be a license violation to restrict. What part of CC-BY-SA or GFDL would let us restrict a reuser from using a users contributions to pull out patterns of purported bad actors? --~2026-51667-44 (talk) 07:51, 29 October 2026 (UTC)
If I remember correctly, you have to sign a disclaimer when creating an account consenting to it(It's been a while since I created my account so I could be wrong here), but the ADL aren't requiring that people consent, which is illegal at least in Australia. This is almost certainly a matter for the lawyers because they are breaking Australian law at the very least, and many Wikipedia editors are from Australia. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 08:06, 29 October 2026 (UTC)
Why would Australian law be a factor? Its an American non-profit doing the analysis, of a website owned by another American non-profit whose primary hosting is in America. There's no nexus to Australia. Having an Australian user isn't enough. The EU tries to claim having European users is enough to apply EU law as well, and despite that claim Wikipedia has no Data Protection officer, and will not turn over all data relating to a person (withholds arbcom deliberations and discussions) as required by the GDPR. Because it operates under US law.
The group has a First Amendment right to do what they do. Other groups have a right to loudly criticize them. They have the right to not work with them. Wikipedia's license does not allow us to stop them doing what they're doing. Nothing in Australian law has any bearing on that. --~2026-51667-44 (talk) 21:02, 29 October 2026 (UTC)
Because Australian law applies to Australian users. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 21:03, 29 October 2026 (UTC)
As the TA says, the Anti-Defamation League are Americans using an American website that operates on American servers. It's still not clear what Australia has to do with this specific case; Australian law only applies to parties who are Australian. (The mere act of analyzing an Australian user on an American site doesn't mean that the analyzer falls under Australian law.) Since neither party is Australian, the presence of Australian law is not relevant here. Accessedgrant (Epicgenius mobile alt) (talk) 03:26, 30 October 2026 (UTC)
Something not being illegal doesn't mean it's not wrong or immoral. It's pretty clear that what they're doing, or planning to do, is POV-pushing via intimidation. sapphaline (talk) 08:58, 29 October 2026 (UTC)
Also, per my post above, it is illegal in at least one jurisdiction. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 08:59, 29 October 2026 (UTC)
It is not illegal to analyse someone's wikipedia contributions. In solidarity, asilvering (talk) 09:02, 29 October 2026 (UTC)
Seemed to me like they were implying that they were stalking Wikipedia editors. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 09:03, 29 October 2026 (UTC)
@Sapphaline There is no disclaimer when you create a Wikipedia account. Every time you publish an edit you agree to the Wikipedia terms of use, which references the privacy policy, which states that your contribution history is a permanent public record, and goes on to say You should be aware that specific data made public by you or aggregated data that is made public by us can be used by anyone for analysis and to infer further information, such as which country a user is from, political affiliation and gender. There is no requirement for your to sign a disclaimer with the ADL or anyone else for them to do analysis of your contribution history. --Ahecht (TALK PAGE) 20:46, 29 October 2026 (UTC)
I may open a discussion at RSN about this per the precedent established with the Heritage Foundation. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 08:09, 29 October 2026 (UTC)
It sounds to me less like they are making a doxxing threat and more like they are announcing that they have been cyberstalking us. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 08:16, 29 October 2026 (UTC)
It contains the usernames, not the names. --Ahecht (TALK PAGE) 20:51, 29 October 2026 (UTC)
Although it shows some poor understanding of Wikipedia and some terrible political positions, it does not give evidence of cyberstalking, of tracking users off-wiki or of attempting to doxx. It is an analysis of the publicly available edit histories. Our editing should be up to such scrutiny, and our public edit history is designed to make it so. BobFromBrockley (talk) 12:38, 30 October 2026 (UTC)
The concern here seems to be that there is an organization with a huge amount of money and political power that is trying to influence and modify what's written on Wikipedia to align with its own world view. This in itself is quite problematic for the same reason that we ban canvassing. Ita140188 (talk) 09:00, 30 October 2026 (UTC)
Just going to link my comment from RSN here - Disturbing if true, but considering the source provided is seemingly an open white nationalist I'm not so sure this should be taken at face value. TheKip(contribs) 11:04, 29 October 2026 (UTC)
Also going to point out here that it's highly suspicious that they're in synagogue attire in a synagogue for a press release and that may be a sign of an antisemitic nutjob using AI to back up their own claims. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 11:08, 29 October 2026 (UTC)
No more than when a Christian wears a cross. Slatersteven (talk) 17:04, 29 October 2026 (UTC)
Eh, no it is in fact weird; at least I find it weird as a Jewish person who has attended synagogues belonging to variety of different Jewish denominations over time. A tallit is only worn in the context of specific prayer services, most of which you wouldn’t normally be filming at. It’s not exactly forbidden to wear in other contexts, but it’s not normal to wear outside of specific rituals. Wearing it for a press release about Wikipedia is weird. If we’re analogizing to Christian practice, I’d compare this to donning a nun’s habit or a priest’s frock as a layperson. signed, Rosguilltalk 17:14, 29 October 2026 (UTC)
The supposed source of the clip is a more general talk, rather than a press event. But there are exactly 0 reliable in this whole matter, so I would lean towards this being some kind of missinfo.MetalBreaksAndBends (One for all) 17:26, 29 October 2026 (UTC)
The timing of the event right after Saturday services makes the wearing of tallesim more normal, although it's a weird time for a Conservative congregation to be having a public, filmed event (but maybe they've changed practice around recordings a bit since COVID) signed, Rosguilltalk 17:30, 29 October 2026 (UTC)
Just irreparably ruined my ad targeting, turns out the clip was from some other event (unreliable sources have accuracy issues, who would've guessed!). But, I think he also mentioned monitoring wikipedia at the Sinai Temple event too? Here's the twitter clip, this one seems a bit more verifiable. I'm pretty sure the other guy on the poster was there for it, as there's another clip where the camera isnt only on Greenblatt. MetalBreaksAndBends (One for all) 17:55, 29 October 2026 (UTC)
This source (infolibnews - Chris Menahan) is the white nationalist conspiracy theorist referred to by The Kip above. We should not be linking to their content. BobFromBrockley (talk) 12:41, 30 October 2026 (UTC)
Only rabbis wear them? Slatersteven (talk) 10:04, 30 October 2026 (UTC)
Editors who promote real-life violence are legitimate targets for FBI surveillance. I'm not the one accusing them of crimes, just they should not be surprised if the FBI comes looking for them.tgeorgescu (talk) 07:04, 30 October 2026 (UTC)
And the relevance of this vague accusation (oh sorry, "I'm not" accusation) to this thread is...? Fram (talk) 09:26, 30 October 2026 (UTC)
Or, the ADL is not the FBI (leave to the law that which is the law business) and promoting killing is against the law and should be reported, not lead just to user bans. Ignoring, what the hell do you mean "promote real-life violence" (see wp:agf). Slatersteven (talk) 10:01, 30 October 2026 (UTC)
If the editors were genuinely "pro-Hamas" they would be promoting real-life violence. The issue is that what ADL counts as "pro-Hamas" is not what most informed humans would. BobFromBrockley (talk) 12:42, 30 October 2026 (UTC)
No, you see, we are defending Hamas... somehow... LightNightLights (talk • contribs) 13:11, 30 October 2026 (UTC)
Note that the Israeli mainstream position is that every member of and supporter of Hamas should be killed. Technology exists to kill anyone deemed pro-Hamas based on the location of their online devices. Refaat Alareer and his family were killed as a result of his social media content. There are many other examples.
The ADL calling editors pro-Hamas, irrespective of it being baseless, should be considered a very serious threat.
The best read I have is: tgeorgescu is defending the ADL and thus is attacking people who are pro-Hamas, as "[e]ditors who promote real-life violence".
Conveniently, pro-Israel violence was not brought up. LightNightLights (talk • contribs) 13:27, 30 October 2026 (UTC)
It is their POV, not mine. tgeorgescu (talk) 13:41, 30 October 2026 (UTC)
This is why we have AGF and should not be accusing any editors of promoting violence (we do not have parliamentary privilege here; you do not repeat random accusations). Slatersteven (talk) 13:52, 30 October 2026 (UTC)
White supremacist editors get quickly shunned when admins find out, but they exist.
@Tgeorgescu: can you please explain what you meant? It sounded as if you were making excuses for the ADL by starting about some unmentioned, unknown "editors who promote real-life violence" out of the blue, but perhaps you meant something else? Fram (talk) 13:37, 30 October 2026 (UTC)
That's what the ADL stated: they want to catch editors who advocate for violence. tgeorgescu (talk) 13:39, 30 October 2026 (UTC)
That's not what the ADL stated though.
"We've had to build software to track, to try to identify where editors are coordinating on edits to again poison the articles on Zionism, to poison the articles on Israel, to poison the articles on the Jewish community, our faith". Fram (talk) 13:52, 30 October 2026 (UTC)
I watched the video: "white supremacists... Christian nationalists..." tgeorgescu (talk) 13:58, 30 October 2026 (UTC)
Which video? You are not talking abou the one-minute one posted on X which started all this, but something else? Fram (talk) 14:06, 30 October 2026 (UTC)
The two minutes one. tgeorgescu (talk) 14:10, 30 October 2026 (UTC)
Do you have a link? Fram (talk) 14:17, 30 October 2026 (UTC)
My point: ADL also does the dirty work for liberals. tgeorgescu (talk) 14:19, 30 October 2026 (UTC)
No idea what you mean with that last sentence, but you seem to be doing the dirty work for the ADL, equating all people who edit against the preferences of the ADL with "people who promote real-life violence". Fram (talk) 14:32, 30 October 2026 (UTC)
Going after extremists who promote violence is not a fault. Of course, that should not get overstepped through crying wolf. tgeorgescu (talk) 14:40, 30 October 2026 (UTC)
No but going after people who do not follow the ADL's POV is (crying wolf). Slatersteven (talk) 14:51, 30 October 2026 (UTC)
"they're monitoring the DSA, anti-war activists, pro-Palestine groups, "right-wing extremists," political Islamists, Christian nationalists, and others." Equating this with "going after extremists" (like you said now) or "people who promote real-life violence" who "should not be surprised if the FBI comes looking for them" is an extremely one-sided POV and basically just amplifying their dubious message. Don't know if this is yoour usual method, but it's a very bad look. Fram (talk) 14:55, 30 October 2026 (UTC)
I think we all agree that the ADL shouldn't cry wolf. tgeorgescu (talk) 14:56, 30 October 2026 (UTC)
I don't think we are reading the same discussion. I don't agree with your stance, and am not interested in finding some tiny sliver where we don't necessarily disagree to make it seem as if we agree here. You made very dubious claims to defend the ADL and attack the editors they try to dox or intimidate, while hiding behind some sophistry.
You stated, in full: "That's what the ADL stated: they want to catch editors who advocate for violence." This is not what they stated at all. I have no interest in continuing debate, never mind "agreeing", with someone who makes such false claims to defend an organisation going after Wikipedia editors. Fram (talk) 15:07, 30 October 2026 (UTC)
But thier own statement makes it clear that is what they are doing, going after anyone critical of Israle. Slatersteven (talk) 15:12, 30 October 2026 (UTC)
tgeorgescu, Wikilawyering that "I'm not the one accusing them..." doesn't play. This is an extemely concerning statement and I highly recommend you strike it as it absolutely does read as you stating that editors are promoting real-life violence and the FBI needs to surveil them, which can at the very least be taken as intended to cause a chilling effect even if it doesn't meet the strict letter of WP:NLT. And that's even completely leaving aside that this is about the ADL, not the FBI, and the ADL, not being the FBI, has not the authority or legal power to surveil a ham sandwich. - The BushrangerOne ping only 22:53, 30 October 2026 (UTC)
Well no more than any other user. Slatersteven (talk) 15:03, 31 October 2026 (UTC)
"Software to track Wikipedians" is likely less complicated/evil than we're imagining. Nor does it mean that its a doxxing tool. Sure, it could be very devious and evil. But its more likely to be some vibe-coded contribution checker. CaptainEekEdits Ho Cap'n!⚓ 20:27, 30 October 2026 (UTC)
Wikimedia Foundation Bulletin 2026 Issue 20
Here is a quick overview of highlights from the Wikimedia Foundation since our last issue on October 9. Please help translate.
Mobile users can now edit with visual editors
Highlights
Community Wishlist: The process for this year’s Community Wishlist has been published, incorporating community feedback. The wish submission process will end on November 8. The triage is expected to be completed by late November. Votes for wishes will start in January.
Behind the scenes: What happened on 25 August as hundreds of edits were made to Dolly Parton's article on English and German Wikipedia – and why code stewardship and the Service Catalog matter.
The new Image Carousel treatment experience that will be tested
Identifying LLM edits easily: LLM Paste Check is now available on all Wikipedias. The feature will notify editors using the visual editor when they paste text that is likely to have initially been copied from one of five external generative AI chatbots. Edits will also be tagged so that patrollers can review them more closely.
The Future of Wikimedia Hackathon:A proposal to hold the Wikimedia Hackathon every three years, with regional hackathons in between has been shared. It explores making the event more accessible to technical communities in different regions. Share your feedback on the proposal’s talk page before November 6.
Re-testing Image Carousel on readers: Starting November 20, a test for Image Carousel will run for logged-out readers. Readers will browse community-uploaded images, selected by editors as relevant to specific articles. It will measure the impact of incorporating some community-requested features on logged-out reader retention.
Changes to Watchlist view: Moderator Tools will be removing the list view of the Watchlist and defaulting everyone to the changelog view. By defaulting to the changelog view, we are simplifying the codebase and avoiding the likelihood of missing bugs.
Wikifunctions quarterly planning: For October–December 2026, Wikifunctions will focus on two main areas: working with pilot communities towards bringing abstract articles into their Wikipedias, and making it easier to create and edit articles on Abstract Wikipedia.
Suggestion Mode: To encourage newcomers to publish their first suggestion when using Suggestion Mode, implementation of the publish prompt on mobile has been completed.
Onboarding newcomers: To encourage new editors to make their first edit, the early onboarding A/B test went live.
Tech News: The latest highlights from Tech News weeks 42 and 43 include CodeMirror syntax highlighting was enabled by default for all logged out and newly registered users on the English Wikipedia. See also the 54 community-submitted tasks that were resolved over the last two weeks.
Open geospatial dataset now released: Wikimedia Enterprise has released an open geospatial dataset containing 17 million OpenStreetMap elements linked to Wikidata, Wikipedia, and Wikivoyage, as Parquet and GeoParquet files on Hugging Face and Kaggle.
Better bot detection: There is a new bot detection system for traffic to the Wikimedia wikis. There might be sudden changes to visitor statistics starting on 26 October and going back to 20 June. This is because we will now be better at finding automated traffic which is trying to hide that it is coming from bots.
The Wikipedia Library: Datawrapper is now available in The Wikipedia Library. This is a data visualisation platform to create and publish responsive charts, maps, and tables. If you're a contributor who qualifies for TWL, please feel free to apply for access and make use of this tool.
For information about the Bulletin and to read previous editions, see the project page on Meta-Wiki. If you have feedback or suggestions about the bulletin, let us know at foundationbulletin@wikimedia.org. For questions about the Wikimedia Foundation's work, contact us!
Hi y'all – we wanted to follow up about the source verification project, where we’ve just completed an internal review of the suggestions it produces and have a proposal about making it accessible for testing with experienced editors.
With your help, we defined criteria to select the 1,000 articles we would generate an initial dataset of source verification suggestions for.
We (staff) have created this dataset and completed an internal review of it.
What follows is a summary of what we found, what we think these findings mean for this work going forward, and the open questions we're left with.
What do you think about the conclusions we've reached and next steps we're proposing?
Conclusions
We reviewed 134 source verification suggestions from the dataset and discussed them together as a team. What follows are the conclusions we're reaching:
Article claim and source URL extraction worked well. Generally, the model succeeded at extracting claims and source URLs from Wikipedia articles. This enabled us to focus on the quality of the verdicts the model reached and the rationale it provided for each.
The model outputs sufficiently reliable verdicts. In 71% of the suggestions we reviewed, internal reviewers agreed the cited source did not fully support the claim, including 49% where it did not support the claim at all. Several of these were concrete discrepancies between article and source (see the Lucille Ball and Alamgir examples below).
Taken together, we think the source verification suggestion is reliable enough to warrant a wider volunteer-led review. Please see "Proposed next steps" for how we see this playing out.
Proposed next steps
With the "Conclusions" above in mind, we see the next steps as the following:
On Tuesday, 3 November 2026, we (staff) make the initial dataset of source verification suggestions available to you all in two forms:
Note: These suggestions would only be available to people who have both 1) published ≥100 cumulative edits and 2) enabled experimental edit suggestions within Preferences
As a spreadsheet so that you can more easily see patterns across suggestions and locate articles where you can experience the suggestions in-context via Suggestion Mode
Note: we do not think reviewing suggestions in the spreadsheet alone is sufficient for forming an opinion about the usefulness of the suggestion.
Note: we see the purpose of y'alls review as making sure we wouldn't be wasting unsuspecting experienced volunteers' time with a large number of erroneous suggestions by enabling source verification suggestions as default-on within Suggestion Mode.
We (staff + volunteers) will then look at data from both reviews to decide: Do we make the source verification suggestion available by default within Suggestion Mode to experienced volunteers so that we can evaluate how helpful they find it in real world use?
Note: to evaluate "how helpful [volunteers] find it in real world use" we would be analyzing engagement with the suggestion, the quality of edits made with it, the edit completion rates of edits where it was activated, and qualitative feedback from experienced volunteers who tried it.
Open questions
What additional filters might be useful to place on the model and/or what articles it runs on to create a more useful user experience? E.g. Setting a cap on how many suggestions are shown per article, preventing suggestions from appearing on list pages, etc.
What information, shown alongside a suggestion, might help you decide more quickly whether it’s right? E.g. deep-linking to the relevant passage within the source, linked to the diff where the claim was added, etc.
Currently if the claim is not supported, we expect that the editor will fix it or add a {{failed verification}}. Is that reasonable or are there other actions we should try to directly enable?
How should the suggestion behave when it can't read a source (e.g. paywalled, offline, etc.)?
Detailed findings
Internal review findings
Process
We generated a total of 16,585 suggestions for a sample of articles that met the criteria listed here
We compiled those 16,585 suggestions into a spreadsheet, split up by category (e.g. blp, history, ctop, {{dubious}}, {{Failed_verification}}, {{ai generated}}, etc.)
6 staff members reviewed a total of 134 of the 16,585 suggestion
For each of the 134 suggestions, staff:
Reviewed the claim text the model extracted from the article and evaluated whether they thought the claim was complete
Reviewed the verdict the model reached (Not supported or Partially supported), the rationale the model gave for why it reached said verdict, determined to what (if any) extent they thought the model prediction was correct, and offered an explanation as to why they reached the conclusion that they did
We then looked over the suggestions our colleagues reviewed and documented general reflections about them
Lastly, we calculated the rates at which staff verdicts did and did not align with the verdicts the model reached (see "Quantitative findings" below)
Quantitative Findings
In 49% of cases, reviewers agreed with model in concluding source does not support claim at all
Flagged claim
Notes
AdventHealth opened a 200,000 square feet (19,000 m2) emergency room and primary care facility on Walt Disney World's campus on May 17, 2023.
"AdventHealth facility is only 19 thousand sqft, not 200 thousand" (page: AdventHealth, check id 3c1bac7e1c82eaae)
[Lucille Ball’s] acting forays were stilled at an early stage when she became ill with rheumatic fever and was unable to work for two years.
"Claim states she had rheumatic fever but source states it was rheumatoid arthritis." (page: Lucille Ball, check id: 3f99f519c8f527fc)
[Mary of Teck] is buried beside her husband in the nave of St George's Chapel, Windsor Castle.
"Queen Mary was buried in the North Nave Aisle, not the nave itself." (page: Mary of Teck, check id 012418710cd2e07e)
"Though Alamgir was unhurt, three vehicles (including the one in which he was riding) were vandalized, and ten people were injured." Link to claim
The claim included within the Wikipedia article states that the car the subject was riding in was damaged. Although, the source cited says the car he was riding in was NOT damaged. These two statements contradict one another. (page: Mirza Fakhrul Islam Alamgir, check id: 01836695cfc49863)
In 22% of cases, reviewers agreed with model in concluding source does not support claim fully
Flagged claim
Notes
On 17 June 2026, Keir Starmer announced that the Children's Wellbeing and Schools Act 2026 has passed, which puts a ban on children under 16 having accounts and accessing social media apps
The act was passed on a different date and doesn’t ban anything by itself (page: Online age verification laws by country, check id: cbeeec4e88959d7a)
[Amis Harvest Festival] takes place every July to September.
Article claims that the Amis Harvest Festival takes place every July to September. The source only mentions summer time, not fixed dates, and that the dates can vary across villages. (page: Amis people, check id: 740542a585970b96)
A statue of Earhart by Ernest Shelton was erected circa 1971 in Los Angeles, California.
Source talks about the statue and when it was erected, but doesn’t mention the sculptor’s name as listed in the claim. (page: Amelia Earhart, check id: 0366ad517930495e)
In 28% of cases, reviewers disagreed with model in concluding source does not fully support claim
Flagged claim
Notes
“Marie Tussaud was employed to make a death mask of her head.” -
The model thought that “her” refers to Marie Tussaud herself (page: Marie Antoinette, check id: 770d5c8b71c195f2)
It would also be played by Weir's RatDog after the dissolution of the Grateful Dead.
Source does say that Ratdog played "Victim or the Crime", and the dates mentioned in the article are after the dissolution of the Grateful Dead. (page: Victim or the Crime, check id: 2d912ad52fc7efe4)
Following the release of Citizen Vigilante in late June 2026 and its ban in Germany, the film was promoted by Elon Musk on X, greatly boosting its reach.
A second source verifies the part of the claim that the model says the source doesn’t verify (page: Uwe Boll, check id: 0e4b8066c9135210)
Qualitative findings
Perceived significance of discrepancies: There are some claims that the model flagged as not being supported by their source(s) that, upon closer inspection, involved relatively small discrepancies between the information included within Wikipedia and the source. Editor opinions may vary on how consequential they consider these discrepancies to be.
E.g. a film reaching some sort of revenue milestone within 3 vs. 4 days after launch.
Selection bias: The quantitative findings should be taken with a grain of salt considering we did not review suggestions randomly. As such, there may be some selection bias at play.
URL Extraction: as part of the initial internal review process, each person was asked to verify whether the model had accurately extracted the source URL from Wikipedia. In 100% of cases, the model was successful in this operation. As a result, we removed this URL checking from the review process.
Claim Density: the number of claims the model flagged as needing review varied article-by-article. Some of this variance can be explained by genuine differences in content quality, others, as we came to learn, can be explained by the model handling claims that start with pronouns (e.g. "he/she") less well. There are a series of improvements we think could improve the model that we'd value y'all input on. See "Open questions" below. For context:
A typical article in our sample has over 150 citations, and the model flagged about 17 of them as not fully supporting their claims.
There are outliers: 2% of articles have >100. Lists and some biographies (e.g. 2026 deaths in the United States - see screenshot). This is due to a combination of the higher background level of sloppiness, citation density and tool deficiencies, for instance the pronoun problem.
Number of Source Verification Suggestions per article (initial en.wiki dataset).Experimental Source Verification Suggestion live in Suggestion Mode.
Suggestion invalidation
Suggestions appear if and only if the claim and source have not changed since the article was initially analyzed and the source is not followed by a qualifying template[i]. That is, if the suggestion has been addressed in any capacity - a user has updated the source or the claim, whether prompted by suggestion mode or not, or has added a qualifying template - then the suggestion will no longer show to any user.
If a user dismisses a suggestion by clicking the ‘dismiss button’, they won’t see that suggestion for the remainder of the edit session. However, they - and other users - will continue to come across it in future edit sessions until it is actually addressed.
The Editing Team recognizes the importance of preventing what experienced volunteers agree are invalid suggestions from appearing for themselves or other people in the future. We are tracking this work in T427236 and T433147. While we have not yet defined a timeline for when this functionality will be in place, you can see the technical thought we've put into the architecture that would help enable it.
i. Wikis have the option to locally configure a ‘templateToInsert’ for Source Verification in the on-wiki config. This is the template that (1) will be inserted after the claim when the user dismisses the suggestion with the ‘suggestion is valid’ response, and (2) will be checked for to determine if the suggestion is still valid and should be surfaced to other users. For example, the recommended ‘templateToInsert’ for enwiki would likely be {{Failed-verification}}.
Hi, does the WMF Tool already have access to the wikipedia library? I testet the script from Alaexis however in all the testet articles, 90% of the sources were not available, even open access sources. If its like that, the tool is useless. While i can certainly copy the text into Alexis's tool and let it be checked, but then I might as well just ask the AI in my browser. Or myself. In my opinion, the tool is only useful if it saves me the trouble of looking up the claims in the sources. Then all I have to do is verify the AI's output. The Other Karma (talk) 07:27, 31 October 2026 (UTC)
I am not sure 71% is sufficiently reliable - that's calling someone out to look specifically at a source to double-check something for no reason more than 1/4 of the time. And since we can't actually dismiss the suggestions, that... will be a lot of incorrect suggestions constantly coming back up.
Re: whether a source agrees fully or not, I'm not really seeing a difference between "agree not fully" #3 (the Earhart one) and "disagree not fully" #3 (Uwe Boll). In both cases, as I read these, there is some information that was not in the source, and the model is equally correct in both instances. It's just that in the second there is also another citation. This will surely affect quite a lot of articles - can the model not be trained to look at all of the footnotes given, not just the first?
Re: "north nave aisle", it's quite normal to describe that part of the cathedral as "the nave". So the claim is actually fully correct, if not as specific as it perhaps ought to be. In solidarity, asilvering (talk) 19:51, 29 October 2026 (UTC)
I am not sure 71% is sufficiently reliable…
You may end up being right in thinking this suggestion is not reliable enough, in its current form, to warrant a deployment as a default-on suggestion within Suggestion Mode.
Although to clarify, we were not seeking, nor equipped to, make a decision about a wider deployment with this initial internal review. This internal review was narrowly scoped to answering, "Do we think these suggestions are reliable enough to warrant experienced volunteers allocating valuable time to reviewing them?"
And based on the review we conducted, we do think the suggestion is reliable enough to invite interested experienced volunteers to review them.
It's only after we (staff and volunteers) have reviewed these suggestions would we together decide "Do we make the source verification suggestion available by default within Suggestion Mode to experienced volunteers so that we can evaluate how helpful they find it in real world use?" (See Step 3 above)
Does this get at the point you're making? Might there be something I'm missing/misunderstanding?
...that's calling someone out to look specifically at a source to double-check something for no reason more than 1/4 of the time.
On the time spent piece, you may well be right and I think it's only through real world use will y'all be able to make a judgement call on this.
As I see it, what matters is whether the time spent checking false positives outweighs the time saved by catching real errors. To what extent (if any) does this thinking align with how you're viewing this tradeoff?
And since we can't actually dismiss the suggestions, that... will be a lot of incorrect suggestions constantly coming back up…
We agree with you here: without the ability to dismiss suggestions, multiple volunteers could see the same unhelpful/incorrect suggestion which would in turn increase how precise the model would need to be before we’d (staff + volunteers) be comfortable putting it in front of people. Potentially, to an unachievable point even.
So it's not ambiguous: we see work on dismissals as a question of when not if and we're open to the possibility that this functionality would need to be in place before source verification suggestions are enabled by default.
Thank you for thinking through this critically. Please let me know if any facet of the above leaves questions/concerns open in your mind or causes new ones to emerge. PPelberg (WMF) (talk) 22:33, 29 October 2026 (UTC)
@PPelberg (WMF), we must be misunderstanding each other, because I read "Do we think these suggestions are reliable enough to warrant experienced volunteers allocating valuable time to reviewing them?" as basically "is this reliable enough to be deployed?" with extra words. What's the difference, for you? In solidarity, asilvering (talk) 02:05, 30 October 2026 (UTC)
@Asilvering, the distinction is between enabling them as experimental suggestions, visible only to editors who have opted in to experimental suggestions, and making them regular suggestions, visible to all editors who meet the edit-count criteria. Alaexis¿question? 07:34, 30 October 2026 (UTC)
Thank you for adding this context, @Alaexis. @Asilvering: does what Alaexis shared above address the confusion you spotted? PPelberg (WMF) (talk) 22:30, 30 October 2026 (UTC)
No, I think we may have a fundamental disagreement. But I think that disagreement could be resolved by reframing how the edit suggestion is presented to editors. Right now, the wording of the suggestion begins from the presumption that the model is intended to highlight problematic sentences; the purpose of this edit suggestion is to find and fix incorrect sentences on Wikipedia. It is understandable that the suggestion is worded in this way, because that was indeed the intent of this project. However, with a 71% hit rate, we cannot truthfully say that the model is highlighting problematic sentences. So in fact what we have is an edit suggestion that fails 29% of the time even if the editor correctly applies WP:V when responding to the check, which we can't be certain about either.
If you cannot raise the hit rate over 71%, the suggestion should be reframed as a spot check. We do sourcing spot checks all the time (for example, at WP:GAN), and they do not start from the presumption that the sentence is incorrect. (At GAN, you're instead starting from the presumption that the sentence is correct, if anything.) So instead of "a model has identified that this claim might not be supported by its source", you end up with something neutral like "a model has selected this sentence for source-checking". Under those terms, you have an edit suggestion that works 100% of the time, and ideally results in improvements to the article 71% of the time or more often. Does you follow?
In any case, we definitely need the ability to dismiss suggestions as incorrect (ie, to mark it as "fact checked, it's fine") before this leaves "experimental mode". In solidarity, asilvering (talk) 00:03, 31 October 2026 (UTC)
I like the idea of carefully framing the suggestion as a prompt to spot-check a citation. As a relatively neutral framing, it could reduce automation bias and increase the chance that a person actually goes and looks at the source. It also opens up the opportunity to prompt spot-checking of sensitive/high-risk statements where the automated verifier can't access or parse the citation. The research for the reference need model (paper) might suggest ways to help find those statements. Dreamyshade (talk) 00:57, 31 October 2026 (UTC)
+1, I assumed this was already going to be the case Kowal2701 (talk, contribs) 01:03, 31 October 2026 (UTC)
Agreed re the dismissal and I think that it should be recorded on-wiki. This way the community will be able to measure the effectiveness of suggestions (edits vs dismissals). Having it recorded will also reduce abuse as the editor will know that the dismissal is recorded and attributed.
Not sure about the framing as "spot checks". Spot checks ("a quick examination of a few members of a group instead of the whole group" ) make it look like a random sample, while in reality it's more like a screening (medicine), where a positive result means that a more thorough check is needed.
I'm sure the language can be adjusted, I think one widely used tool that has the same probabilistic nature is Earwig's Copyvio Detector. It describes likely copyvios as "Violation suspected" (example - here the top one is actually not a copyvio but a wiki mirror). Alaexis¿question? 17:20, 31 October 2026 (UTC)
Re: whether a source agrees fully or not, I'm not really seeing a difference between "agree not fully" #3 (the Earhart one) and "disagree not fully" #3 (Uwe Boll). In both cases, as I read these, there is some information that was not in the source, and the model is equally correct in both instances. It's just that in the second there is also another citation. This will surely affect quite a lot of articles - can the model not be trained to look at all of the footnotes given, not just the first?
Good catch. The model is trained to evaluate all footnotes following a claim, not just a subset of them. If it happens to return a verdict that doesn't cover the complete set, then we do a second check on the suggestion mode side to ensure this suggestion isn't shown to users. So this example is one that was not caught by the model but would still not have been shown in suggestion mode; including it as an example here was our mistake, as it doesn't reflect the actual user experience. CMedelius-WMF (talk) 22:47, 29 October 2026 (UTC)
With regards to #1, I think it'd make sense to avoid checking articles being rapidly edited, new articles, and claims that cite paywalled or offline sources as referred to in #4. On #2, making the model's reasoning available could help the community figure out where strengths and weaknesses are. MetalBreaksAndBends (One for all) 19:57, 29 October 2026 (UTC)
On #2, making the model's reasoning available could help the community figure out where strengths and weaknesses are.
@MBAB, could you please say a bit more here about the sort of reasoning you'd find helpful?
I ask this because currently, the model outputs a rationale for each suggestion it outputs. E.g. “Claim states she had rheumatic fever but source states it was rheumatoid arthritis”. This leads me to think you might be thinking of something else/in addition...
I think it'd make sense to avoid checking articles being rapidly edited, new articles...
You and @CMDeach raised this. Could you please share a bit more about where this recommendation is coming from?
For what it's worth, we'd been assuming (perhaps inaccurately!) that it'd be useful to check articles that are new and being rapidly edited because they'd be more likely to contain inaccuracies. Then again, maybe you're thinking adding another actor into these situations (in this case a machine) could complicate things? PPelberg (WMF) (talk) 23:46, 29 October 2026 (UTC)
I was talking about reasoning tokens, as reading them can be helpful for understanding a model's thinking in further depth than a 50 word summary can provide. Obviously, this shouldn't be exposed to editors by default (especially if your model of choice has a GPT-6-astra-esque affinity for not using the spacebar).
I suggested avoiding rapidly edited and new articles for 2 slightly different reasons. New articles because they're going to be in the NPP queue, which means they're going to be checked soon (although ai verification built for the NPP workflow could be promising. e.g. not doing the check until the page is being reviewed and factoring in other steps like a source's value for notability). For rapidly edited articles, it's because there's a higher chance that any given checked text will be modified requiring rechecking. My concerns on both of these is less that the system might get something wrong and more that compute might be misallocated. MetalBreaksAndBends (One for all) 00:26, 30 October 2026 (UTC)
I was talking about reasoning tokens, as reading them can be helpful for understanding a model's thinking in further depth than a 50 word summary can provide. Obviously, this shouldn't be exposed to editors by default...
Ah, got it. I agree with you in thinking that exposing this level of detail is best suited for somewhere deeper in the experience so folks who are especially curious can find it. Thank you for adding this context.
In case it's interesting to know: I think the checks we ran used an un-reasoning version of Qwen 3.8. Although, @SSalgaonkar-WMF will be able to say for certain. PPelberg (WMF) (talk) 22:33, 30 October 2026 (UTC)
I suggested avoiding rapidly edited and new articles for 2 slightly different reasons. New articles because they're going to be in the NPP queue, which means they're going to be checked soon (although ai verification built for the NPP workflow could be promising. e.g. not doing the check until the page is being reviewed and factoring in other steps like a source's value for notability).
Understood. To confirm the NPP use case, you're thinking that it would be worthwhile to wait to run the suggestion on new articles until after an experienced volunteer has validated the article meets notability requirements? Specifics aside, we're with you in thinking there is/are NPP-specific use cases here that feel promising.
For rapidly edited articles, it's because there's a higher chance that any given checked text will be modified requiring rechecking. My concerns on both of these is less that the system might get something wrong and more that compute might be misallocated.
Oh, okay. I see. Understood. Thank you for explaining that. PPelberg (WMF) (talk) 22:37, 30 October 2026 (UTC)
...and claims that cite paywalled or offline sources as referred to in #4.
Right now, the suggestion ignores offline and paywalled sources. Although, this leads me to wonder: can you see it being useful for the UI to indicate when the model tried to evaluate a claim and was unable to do so because a source was offline or paywalled? Do you think it ought to instead show nothing silently? Something else? PPelberg (WMF) (talk) 23:49, 29 October 2026 (UTC)
This is also mostly based in compute allocation, although there is also a volunteer allocation angle too. If a paragraph has multiple citations at the end with one or more being inaccessible, it can't be known if any given claim not supported by the accessible sources is actually unsupported or just supported in the inaccessible ones. So, for those paragraphs any given suggestion is less likely to be helpful, due to it only being trustworthy where the content explicitly contradicts a source. A flag for inaccessible sources would help avoid errors where correct content is removed because inaccessible sources were skipped. But unless a system were devised to direct verifiers with access to inaccessible content to suggestions, I think bailing at the first sight of problematic sources would offer the best rate of "tokens per abstract unit of improvement". MetalBreaksAndBends (One for all) 00:57, 30 October 2026 (UTC)
I've been working with a Master students evaluating the script, and they found a couple of categories of mistakes it often makes. I will ask them to share. Perhaps that can raise the 71% to a higher level. I agree that 71% is not quite the accuracy we would like to see. Source verification is incredibly time-consuming as an activity, and newish (100-1000 edits) editors are also not great at it. Will this result in properly cited text being removed?
In my two GAs I've run it on today, I disagreed with all 5 suggestion that things were wrong (2 were subjective), but maybe the script uses a different model than the one you have access to? In solidarity, —Femke (talk) 🐦 21:19, 29 October 2026 (UTC)
...I disagreed with all 5 suggestion that things were wrong (2 were subjective), but maybe the script uses a different model than the one you have access to?
@Femke: might you be able to share the version of the script and/or model you were using so that we can check if they're the same? Also: might you be able to share the following so that we can see the suggestions you encountered? It'd be helpful to know:
The permanent link to the version of the article you were editing
The text of the claims the model generated suggestions for
The verdicts and rationale the model gave
I've been working with a Master students evaluating the script, and they found a couple of categories of mistakes it often makes. I will ask them to share.
Seeing what they've found would be a big help. Thank you for offering!
I agree that 71% is not quite the accuracy we would like to see. Source verification is incredibly time-consuming as an activity, and newish (100-1000 edits) editors are also not great at it. Will this result in properly cited text being removed?
I'm going to hold off on responding to the "71% accuracy" part for a moment because I'm going to come back to that in a response to the point Asilvering raised about this above. Now, with regard to who the proper audience might be for this suggestion, we think y'all are best equipped to decide and implement what you think is best via Special:EditChecks. PPelberg (WMF) (talk) 21:41, 29 October 2026 (UTC)
I would love 100+ edits to be the audience, as that's the type of editors we want to teach to fact check everything. But.. I think putting the weapon in their hands would be a bit too dangerous as is. I suspect many people will trust the tool, and where the tool is wrong, it's usually in more complicated facts I also think editors will get wrong.
I'm off to bed soon, but I ran it on post-exertional malaise (4 claims flagged as incorrect) and Ursula Bethell (1 claim flagged). Two of the errors seems to be, if I understand it correctly, from sentences supported by two sources, where 1 of the sources didn't completely cover all the content. One said that 'irreversible decline' was not the same as 'permanent decrease', which is probably a bit more subjective as permanent may be a slightly stronger word, but I'd say that's the same. Don't remember the other two, would have to rerun. Will rerun tomorrow with the requested info.
I used Aleaxis' script with the default settings, so Lift Wing. In solidarity, —Femke (talk) 🐦 21:50, 29 October 2026 (UTC)
For reporting issues that you notice from particular suggestions, it may be easier to use the tool's built-in "comment" button, which sends reports to User talk:Alaexis/AI Source Verification with metadata about the suggestion itself. Sdkb‑WMFtalk 18:39, 30 October 2026 (UTC)
The edit suggestions have a different UI which doesn't have a comment button (see the screenshot above). @CMedelius-WMF, maybe you can explain what options the editor has and how they work? Alaexis¿question? 19:17, 30 October 2026 (UTC)
Yes, the edit suggestion appears with two options: "Revise", which brings them into a focused edit state, and "Dismiss", which opens up a survey to provide an answer on why.
It also has the normal dropdown that is shared by all edit suggestions, which contains an option to provide feedback that is then posted to mw:Talk:VisualEditor/Suggestion_Mode/Feedback. We've internally been discussing a change to make the feedback destination configurable; and in this case, it may be helpful to direct feedback to User talk:Alaexis/AI Source Verification. CMedelius-WMF (talk) 19:48, 30 October 2026 (UTC)
I would love 100+ edits to be the audience, as that's the type of editors we want to teach to fact check everything. But.. I think putting the weapon in their hands would be a bit too dangerous as is. I suspect many people will trust the tool, and where the tool is wrong, it's usually in more complicated facts I also think editors will get wrong.
1) It's important newer editors be equipped with the know-how and tools to help out with verifying claims are corroborated by their accompanying sources
2) I see potential in this suggestion helping newer editors onboard into and complete this work
3) Before "2." can happen, we need to be confident that the user experience is – let's call it – resilient to people assuming the suggestion is always right.
Assuming the three points above accurate reflect the points you were making @Femke, I think we're aligned here. PPelberg (WMF) (talk) 22:45, 30 October 2026 (UTC)
Great to see this work continuing and progress being made.
For my part, idk if ~70% is too low or not. Obviously, higher is ideally better, but I think most people aren't right 70% of the time, so seems to me the model is doing pretty good:-)
The concern I have is that ~150 out of 16k is a tiny percentage, and as they were apparently not randomly selected, I'm not sure if the results are representative at all of anything. Of course, the solution to that is what you're already planning to do: have more people do more testing, which seems like the right next step regardless. Levivich (talk) 22:01, 29 October 2026 (UTC)
yeah, ~70% is well worth it, way better than any other way we have of finding WP:V failures (which is nothing). Issue is whether people will put absolute trust in it or be lazy/go with the balance of probability and not actually read the source before removing stuff Kowal2701 (talk, contribs) 00:50, 30 October 2026 (UTC)
@Kowal2701, that's true for, say, Alaexis's userscript. I'd be quite happy to use a userscript with a 71% hit rate, because I'd be using that mostly informationally - ie, my use case is that I'm already trying to fact-check the article, and the script would be helping me focus on the parts that seem most likely to be wrong. That's great. But in Suggestion Mode, what it's doing is surfacing an error to an editor, possibly a relative newbie, and directly asking them: hey, does this source verify, because I don't think it does? And that's a very different kind of mode that ought to have a higher hit rate than 71%, in my opinion. In solidarity, asilvering (talk) 02:03, 30 October 2026 (UTC)
@Asilvering, agreed that default-on suggestions is a different mode from a userscript. However right now these suggestions will be experimental, visible only to opted-in users, and the whole point of the experimental stage is to check whether these suggestions work before anyone decides to make them regular ones. It's quite possible that based on the findings of the experimental stage we'd fine-tune the pipeline and/or enwiki could raise the edit count threshold. Alaexis¿question? 07:43, 30 October 2026 (UTC)
I think people should easily be able to opt-out of it. Tbh what I don't like about Alaexis' script is reading the LLM's reasoning, I'd rather it just listed the claims with their corresponding sources, possibly on the talk page, and people can just {{tick}} or {{cross}} and sign or whatever. I expect its false positive rate is much higher on good quality articles, we could exclude FAs and GAs but idk what else Kowal2701 (talk, contribs) 15:20, 30 October 2026 (UTC)
...hat I don't like about Alaexis' script is reading the LLM's reasoning, I'd rather it just listed the claims with their corresponding sources, possibly on the talk page, and people can just Y or N and sign or whatever...
@Kowal2701: the simplicity of the workflow you're describing resonates with me and I'm curious: what don't you like about seeing the LLM's reasoning? E.g. might you not trust it and therefore find its presence non-additive?
...I expect its false positive rate is much higher on good quality articles, we could exclude FAs and GAs but idk what else...
The thinking there being those articles have already been closely reviewed by knowledgable volunteers? PPelberg (WMF) (talk) 17:14, 30 October 2026 (UTC)
what don't you like about seeing the LLM's reasoning? Yeah, partly because I wouldn't trust it, partly because I'm sick to death of reading AI-generated text lol. I don't think there's really any benefit to it since in all cases the human will have to check the source for themselves anyway, though ofc having the reasoning is useful for testing the feature re: how accurate it is.
The thinking there being those articles have already been closely reviewed by knowledgable volunteers? Yes, and content written by experienced editors is usually of a similar calibre. Maybe we could use the mw:WikiWho API to exclude content written by editors who have GAs/FAs, or if we wanted it to be more restrictive exclude content authored by users w autopatrolled? Kowal2701 (talk, contribs) 18:24, 30 October 2026 (UTC)
One of the findings from my student this summer was that the script detected loads of issues at a FA that they believed were true errors. I'm curious to see whether I agree. In solidarity, —Femke (talk) 🐦 18:29, 30 October 2026 (UTC)
yeah, I'm sure it would identify true WP:V issues in FAs and content by users w autopatrolled, but given such issues generally occur less often in such content I assume there'd be a higher rate of false positives? Kowal2701 (talk, contribs) 18:32, 30 October 2026 (UTC)
Yeah, you're right that there will be more false positives in such articles (the false discovery rate would be higher). On the other hand, it's also more embarrassing to have such errors in GA/FA, so fixing them may be worth extra time spent on checking duds, and Femke’s student found real errors at an FA. I think it's worth tracking this while the suggestions are in the experimental phase: errors fixed vs discarded suggestions in GA/FA. Alaexis¿question? 18:58, 30 October 2026 (UTC)
it's probably worth incorporating it into GAR/FAC instead of random spotchecks Kowal2701 (talk, contribs) 22:37, 30 October 2026 (UTC)
@Kowal2701, I don't think that's a good idea, because the script only works on a subset of sources, and that subset of sources is already the set that are easier to check. Because reviewers who make random spotchecks are often quite determined to maintain that randomness, they will request access to harder-to-find sources from the nominator and go digging where otherwise they might not, and this is an important part of that process. Alaexis's script can be perfectly useful at GAN/FAC, especially if you're pretty sure the whole article is dubious and you're looking for some low-hanging fruit so you can fail the review and send it back for more editing. But that random spot-check has real benefits and it would be a mistake to incorporate this script instead. In solidarity, asilvering (talk) 00:13, 31 October 2026 (UTC)
Another thing, we might want to exclude articles with {{AI-generated}} tags, since it's not really fair to have someone hone/polish such content when it'll have to be removed or rewritten from scratch Kowal2701 (talk, contribs) 18:30, 30 October 2026 (UTC)
Oh, the notes are the AI's reasoning. Here I thought it was the reasoning of the staff who had agreed or disagreed with the model. That makes me much less grumbly. Though I still think 71% hit rate is far too low for a useful edit check. In solidarity, asilvering (talk) 20:26, 30 October 2026 (UTC)
The concern I have is that ~150 out of 16k is a tiny percentage, and as they were apparently not randomly selected, I'm not sure if the results are representative at all of anything. Of course, the solution to that is what you're already planning to do: have more people do more testing, which seems like the right next step regardless.
Very fair - the results of our internal review shouldn't be taken as a measure of overall accuracy, for the reasons you've stated. However, the purpose of the internal review was more so to perform a sanity check that the suggestions were good enough to be worth additional reviewers’ time. We see volunteer review as the next step because we think you all, as people experienced with verifiability work, bring the nuance needed to differentiate between suggestions that identify genuine issues and those that you'd consider noise. CMedelius-WMF (talk) 08:23, 30 October 2026 (UTC)
For question 1, I agree with MBAB, an automatic tool should avoid frequently edited articles (if someone wants to run it manually, they know what they might be getting into). I don't see a problem with running these on all lists, if the question is whether the tool can understand table sourcing then have it avoid tables on all articles. For question 2, the linked diff is very helpful, especially as it will pick up WP:TSI issues where sources and text get separated by later edits. For 3, please include a nudge for an editor to use the |reason= parameter in fv. For 4, shouldn't the tool simply avoid those situations? More broadly, there seem to be different categories of errors that could be picked up, and it might be useful for the model to distinguish. Of the four "does not support claim at all", the first seems a case of somehow putting in the wrong units. I've found these sorts of numeral mismatches something that models are good at picking up with relatively few errors, if the model can figure out if something counts as a numeral mismatch that might provide a useful subset. The rheumatic fever is another sort of mismatch, worth flagging and seems correct in this case but it seems vulnerable to an llm not understanding wider context. The nave example asilvering has mentioned above, our nave article describes "nave" as having sensu strico and sensu lato meanings, this is perhaps an llm not understanding context and being overly prescriptive. The fourth example is a mix of numbers and prose, harder to classify. However, I don't see how it is distinguished from "does not support claim fully", as the source does support other parts of the text, such as the individual being unhurt. CMD (talk) 23:11, 29 October 2026 (UTC)
In general, I like these next steps. I think that they're reasonable and would allow a much better analysis of reliability. I would guesstimate that in my own experimentation with Claude, about 75% of its suggestions on source-text matches are accurate, so your findings so far roughly track my own experience. In terms of answers to the questions, I think a cap on suggested edits per-page, per-editing-session, is reasonable and that a link to a relevant passage would be helpful. I think if the model/suggestion cannot access a source, it should not take any action to avoid a situation where a new editor also cannot access the source and improperly removes a valid claim. ThadeusOfNazereth(he/him)Talk to Me! 23:39, 29 October 2026 (UTC)
WMF's amicus brief in In re: OpenAI, Inc. Copyright Infringement Litigation
The Wikimedia Foundation filed a motion to submit an amicus brief (Commons link) in the consolidated In re: OpenAI, Inc. Copyright Infringement Litigation case (including e.g. The New York Times v. Microsoft and OpenAI). There is also a summary on Diff.
My read (IANAL) is that the WMF's position boils down to:
Scraping is about access and Terms of Use, and is not a "use" in the sense of "fair use".
Using data to pre-train a "general purpose" model is fair use.
Retrieval at query time is not fair use.
And now here's my take on these positions, and some implications (again, IANAL):
The claims of the publishers that tie copyright to acquisition fail, but server load is a consideration. This is already more or less the WMF's de facto policy.
Disagrees with the New York Times' (and others') core claim. This is the surprising position in my view, both because of the claim itself and even more so because taking a position on this matter just doesn't seem like it was necessary. I would be curious to hear more about why the WMF did so. The Diff post says it's to support smaller-scale/independent AI development. We do rely on machine learning for a variety of maintenance tools, as the brief's conclusion talks about, but there doesn't appear to be any attempt in the brief to distinguish between those small/open developers and the largest corporations that stand to profit the most. #3 claws back some of the traffic lost to AI interfaces, but #2 concedes the rest of it is ok. More importantly, this means prioritizing developers above the journalists and publishers that we depend on for our citations. It's not an easy needle to thread, but it also didn't seem like this particular needle needed threading right now.
This is the consequential position for us, because a chatbot would be able to retrieve Wikipedia content, but would need to provide attribution or a backlink. That would be a Very Good Thing, though I have no idea what the effects of ShareAlike would be within a chatbot answer. For the non-free stakeholders, this would mean retrieval needs a license, which is good for them. Unclear what it would do to retrieval practices in general. Overall, this seems worth the brief itself.
Almost certainly, the third point was the main point, but that leaves the question of what purpose the other two serve. Perhaps the combination reinforces Wikimedia Enterprise? Do the first two make it easier to take the third position? Is there also a strategic-pragmatic move here, knowing that the claim that training is fair use is almost certain to be held up in the long run (given how much of the US economy could be argued to depend on it right now), so conceding that to gain a better position for #3?
I hope none of this sounds cynical, and I hope I haven't misrepresented anything. I found #2 perplexing, but I have a lot of faith and respect in WMF Legal, who I concede may be playing chess while I'm playing checkers. Just hoping for more context. —Rhododendritestalk \\ 19:16, 30 October 2026 (UTC)
I'm also concerned about #2. As I understand it, the thinking is this: if no one can train open source models because a) models trained on copyrighted material cannot be used to generate free material and/or b) it is extremely expensive to acquire training data and small-scale developers can't pay for it, the only game in town will be the big AI companies with the ability to pay, and this would be bad for the free culture movement broadly speaking. In solidarity, asilvering (talk) 21:16, 30 October 2026 (UTC)
This is pure speculation, based on nothing but gut feeling, but one possibility about #2 is that WMF is afraid that if training an AI model on copyrighted material is viewed as copyright infringement, writing a Wikipedia article with sources that happen to be copyrighted would be infringement too. There not being a light-and-day difference between "AI training" and "writing adequately sourced Wikipedia articles". Jo-Jo Eumerus (talk) 13:19, 31 October 2026 (UTC)
The crux of the copyright complaint for the training part of the case has to do with making copies of the copyrighted content first, even if the output isn't a direct violation. Still, that's not a bad take - that the WMF could be taking principled opposition to a copyright/ownership claim that's concerningly broad, given the work we do? —Rhododendritestalk \\ 13:46, 31 October 2026 (UTC)
Makes sense, if it were established that taking information from a copyrighted source was enough to make a copyright infringement, this would seriously imperil Wikipedia's content. Although I don't get the impression that "copies of the copyrighted content first" are the issue per se, at least per The New York Times v. Microsoft and OpenAI? More when (parts of) these temporary copies end up in the reply to a prompt, although from the way the complaint about competition is worded, it may extend to replies that don't meet substantial similarity but share the same information. Jo-Jo Eumerus (talk) 14:06, 31 October 2026 (UTC)
FWIW the replies that contain obvious infringement are the smoking gun, so are very prominent in coverage of the case. They are indeed the subject of copyright claims themselves, but they're also direct support for the much broader claim that training involves making/keeping copies. —Rhododendritestalk \\ 14:26, 31 October 2026 (UTC)
As an experiment, I asked Claude to write an article for me. The prompt I used was:
Write me a Wikipedia article about the SoHo Weekly News, which was an alternative newspaper published from 1973 to 1982 in New York. The article should be about 5000 words long and comply with the Wikipedia MOS (Manual of Style).
I used SWN as a test subject because I had written on the topic myself (shameless self promotion: SoHo Weekly News is going to be on WP:TFA in about a week). I'm not sure what I expected, but the result was kind of shocking. I'll have the WP:AINB folks breathing down my neck if I post it on-wiki, so I tossed a PDF into Google Drive. It's pretty much the poster child for WP:CLOP if not straight-out plagiarism. This may be an extreme case, however. SWN is a niche topic, so there's not a lot of long-form content out there about the paper. My article probably swamps the training corpora on the subject, so I guess it's not surprising that all Claude could do is regurgitate it back.
I get what the NY Times is upset about. The product they sell is partly their investigative reporting and partly their writing. If the LLMs ingest NYT material and spit it back out in the same words (similar to what Claude did with my SWN article), that's clearly copyright infringement.
The deeper question is what if the LLMs ingest a NYT article, understand the information it contains (leaving aside for the moment that LLMs don't really "understand" things in the way we typically use the term) and create entirely new text based on their understanding. That's exactly what I did with my sources when I wrote my SWN article. So, not copyright infringement, but possibly a violation of the NYT Terms of Service which says "The contents of the Services, including the Site, are intended for your personal, non-commercial use". And later on, "Non-commercial use does not include ... the development of any software program, model, algorithm, or other generative AI tool ..." It's really hard for me to see how what the LLMs are doing is not in violation of that. I maintain a paid subscription to the NYT. It's a contract. I give the NYT money. In return, the NYT provides me with certain services, and imposes certain restrictions on how I may use those services. If I don't like the restrictions, I'm free to cancel my subscription and stop using the services.
While I'm certainly sympathetic to the WMF's claim of "fair use", I don't see how that overrides the limitations imposed by, for example, the NYT TOS. I'm also torn between wanting the WMF to be right and wanting the NYT to be right. For sure, I'm all about "information should be free", and I'm certainly preaching to the choir on that one. But I also value the information I get from the NYT (and other papers to which I maintain paid subscriptions). If the NYT is ultimately unable to maintain profitability, they will go out of business and I will lose access to a service I value. I don't want to see that happen. RoySmith(talk) 15:50, 31 October 2026 (UTC)
That sounds like an issue with ToS violations (->contract law?) and not with copyright law, though? Even if it was found that OpenAI violated the NYT TOS, that would not imply that this violation constitutes copyright infringement. This lawsuit seems to be about copyright issues not ToS. JoJo Eumerus mobile (main talk) 16:23, 31 October 2026 (UTC)
In my (non-legal advice) understanding, you are correct that fair use concerns do not override agreed-upon contract terms. As JoJo Eumerus says, the two are separate concerns. If the companies obtained their copies of the copyrighted work without entering into a contract with the publisher, though, then only the copyright concerns are applicable. isaacl (talk) 16:46, 31 October 2026 (UTC)