User talk:DErenrich-WMF/Add A Fact Experiment
Please feel free to leave feedback here!
Thanks DErenrich-WMF (talk) 15:50, 9 August 2024 (UTC)
'Spam' concerns?
My initial gut reaction to this is that it seems great, but I also see how it could, especially on breaking stories, pollute talk pages with impetuously created topics from users acting in good faith but without much consideration. Mittzy (talk) 20:54, 26 September 2024 (UTC)
- Oh, and I do hope that there are not plans to create a similar app that modifies articles directly. While automated edits are useful for housekeeping, I think that major (non-minor per WP:MINOR) changes to a page should be authored with care. Mittzy (talk) 20:57, 26 September 2024 (UTC)
- Agreed on the above, @Mittzy! Tod Robbins (talk) 21:07, 26 September 2024 (UTC)
- AFAIU, currently this requires an autoconfirmed wikipedia user, so the spam potential is reduced.
- It could perhaps also be nice if the extension could check if talk page has a mention of this, then offering to add it as a reply to it (if the source is not the same). Aveaoz (talk) 21:47, 26 September 2024 (UTC)
- I think we've seen from newcomer tasks that any structure that encourages specific editing behavior will produce a significant volume of non-constructive edits. Volume alone doesn't tell the whole story here, as some edits are less constructive/more destructive than others. With that in mind, I think both that and this have the potential to be a net positive for the site, while not unduly burdensome for those trying to maintain the existing quality of articles. Remsense ‥ 论 05:02, 27 September 2024 (UTC)
Thanks everyone for the feedback! This is all really helpful. Yeah polluting/spamming talk pages is definitely something we're thinking about and we're thinking that the talk page might not be the right long term place for this kind of information. If we decide to move forward with this concept we'd definitely want to check that duplicative facts are not being added (either just not letting you add the source or adding it as a reply). Currently the edit rate is low enough that we skipped that for the purposes of getting this in people's hands quickly. DErenrich-WMF (talk) 05:29, 27 September 2024 (UTC)
- One other concern I hold is that Wikipedia can be a highly technical / in-depth resource... The potential for largely automated inclusion of short 'fact' or 'fun-fact' type segments in the middle of an article does not, I feel, fit too well with Wikipedia's goal. As I said last night, I think that such automated / 'AI powered' tools poses quite a risk to the integrity of Wikipedia if it is ever allowed to be used to directly edit articles. Mittzy (talk) 15:12, 27 September 2024 (UTC)
- Thanks for the sharing your thoughts @Mittzy! Did you get a chance to try out the extension and play around with fact/claim selection? It's interesting that you mention "short 'fact' or 'fun-fact' type segments" because our intention was to facilitate adding important new information on topics that may not have yet been updated, not fun facts or trivia. There are many articles (especially on less-popular topics) that haven't been updated to reflect new information/sources because no Wikipedian is closely watching/working on them, but people might be encountering new information on these topics outside of Wikipedia.
- But I can see how adding random fun facts could be something a user of this could do. Tangentially related to this experimental browser extension (which we're just demoing/getting feedback on, not planning to make available to non-editors), but I am curious if you think there is any place anywhere on Wikipedia (maybe not in the article directly) for non-Wikipedians being able to submit well-sourced "fun facts/trivia"? I.e. something like a reader version of DYK? Maryana Pinchuk (WMF) (talk) 20:49, 27 September 2024 (UTC)
- Hey! I have downloaded and looked at the extension, but have not used it to add anything to the site as of yet. I agree with what you say and understand the intended use of the extension, my concern was more related to what would happen if the extension became popular among 'reader' users, and people were to submit lots of insubstantial tidbits (This is what I meant by "fun-fact", though I do admit it was a poor choice of words by me) and pieces of information that are technically true but not substantial enough to warrant inclusion.
- Though, as you say, a dedicated place for non-wikipedians to submit well-sourced fun facts (now using the term fun fact to mean trivia) would be a wonderful thing. I'm not aware of such a place, but the idea sounds like it has a lot of potential. :D Mittzy (talk) 22:03, 27 September 2024 (UTC)
Does not function on Opera GX
I immediately downloaded this extension onto my Opera GX browser after being intrigued by the demo video and tested it out. I searched for an external website I'd been looking at for a while, highlighted a sentence and clicked the extension icon, but nothing happened. I tried toggling all sorts of settings to no avail. Am I doing something wrong or is the extension just not compatible with Opera GX? SleepDeprivedGinger (talk) 21:17, 26 September 2024 (UTC)
- Hey, thanks for the feedback. We did not test this on Opera GX and I do not have a lot of experience with that browser so it's not surprising that it doesn't work. That said I don't think we did anything that would make it explicitly not work. DErenrich-WMF (talk) 05:32, 27 September 2024 (UTC)
- That's alright, do you at least plan on adding support for this browser in future? SleepDeprivedGinger (talk) 11:59, 27 September 2024 (UTC)
- there are no concrete plans at the moment. if we decide to turn this experiment into a permanent project then these are the kinds of things that we'd work on. DErenrich-WMF (talk) 21:38, 27 September 2024 (UTC)
- That's alright, do you at least plan on adding support for this browser in future? SleepDeprivedGinger (talk) 11:59, 27 September 2024 (UTC)
Safari support
I use Safari and would try this extension out if it had a Safari version. I understand that this would require quite a lot of extra work, so it might make sense to hold off on Safari support until and unless Add A Fact exits the experiment stage. Once that happens, reaching as many editors as possible should be a priority, and I hope that the existing Wikipedia app and Apple developer account can streamline the process of getting the extension onto Safari. Ilovemesomenachos (talk) 02:44, 27 September 2024 (UTC)
- Yeah we targeted Firefox and Chrome first because of their wide use in the community. Wider support would be on the table if this exits the experimental stage. DErenrich-WMF (talk) 05:34, 27 September 2024 (UTC)
Oppose on principle
Just logging that I opposed any use of "AI" on Wikipedia on principle, for reasons that should be obvious. MRSC (talk) 04:03, 27 September 2024 (UTC)
- I remain similarly opposed to AI LLMs directly adding content to Wikipedia, especially because of model collapse as AI bots could begin training themselves on potentially incorrect portions of Wikipedia that other AI bots wrote. However, I think you should give this proposal a second look, since this AI implementation only checks whether a statement is already represented on the articles that seem most closely related to the claim. If the statement does not seem to be represented, then human users receive the option to use a non-AI script for proposing the fact to talk pages. BluePenguin18 🐧 ( 💬 ) 07:16, 27 September 2024 (UTC)
- I'm also inclined in principle against AI in Wikipedia. But I'll try to keep an open mind, and will at least give the extension a try. Mike Marchmont (talk) 12:08, 27 September 2024 (UTC)
- Hey, thanks for the feedback even when it's negative. I would actually appreciate more detail on your reasons for opposing applications of AI in Wikipedia. AI is actually already in use in various ways e.g. vandalism detection and is planned for more applications (see [1] or [2]). It'd be useful to know why the community opposes it (e.g. is it energy use, copyright. reliability, etc). DErenrich-WMF (talk) 15:46, 27 September 2024 (UTC)
- The worst problem is a positive feedback loop on "info that's popular" as opposed to "info that's notable and verified" - LLMs introduce a severe information pollution problem. Conformism at its worst. "Four legs good, two legs bad" - it's true because it's true, because that's what everyone says.
- Climate emergency - yes, that's a good argument against supporting LLMs that are racing us towards the tipping points in the climate system.
- copyright violation: Llama (language model) sounds very much like taking from the commons and enclosing it: assuming that LLaMa 2 builds on LLaMa 1, then it's based on CommonCrawl, Wikipedia, "source code from GitHub", public domain material from Project Gutenberg, and other sources, so the use of LLaMa3 (edit) output strings is effectively a massive WP:COPYVIO. Even if it's not inserted into articles, that makes WP:COPYVIO look hypocritical.
- Could you please point to the RfC on en.Wikipedia where this proposal was approved prior to being inserted in the rendered form of en.Wikipedia pages to logged-in users? Or was this a WMF idea imposed on the community without prior approval? Boud (talk) 23:02, 27 September 2024 (UTC) (minor edit to clarify Boud (talk) 13:46, 29 September 2024 (UTC))
- Regarding copyright violation: this extension uses the LLM exclusively to search Wikipedia for articles related to the selected text and to check if the claim is already present in the article. It doesn't output any text. it's also Llama3, not that it changes anything Bertaz (talk) 21:47, 28 September 2024 (UTC)
- There is a WP: space page somewhere that says that we're not supposed to link to any websites known to violate copyright. But here you are proposing that directly benefiting from massive copyright violation should be encouraged. If the LLM exclusively searches Wikipedia, then why not use an LLM trained just on Wikipedia instead of LLaMa3, which is severely polluted by general web content (CrowdCrawl)? That would look a lot less hypocritical in terms of WP:COPYVIO. Llama (language model) says that LLaMa3 is based on text generated from LLaMa2, but doesn't state the dependence of LLaMa2 on LLaMa1, which is why I mentioned the latter as a caveat. Boud (talk) 13:46, 29 September 2024 (UTC)
- Regarding copyright violation: this extension uses the LLM exclusively to search Wikipedia for articles related to the selected text and to check if the claim is already present in the article. It doesn't output any text. it's also Llama3, not that it changes anything Bertaz (talk) 21:47, 28 September 2024 (UTC)
- The worst problem is a positive feedback loop on "info that's popular" as opposed to "info that's notable and verified" - LLMs introduce a severe information pollution problem. Conformism at its worst. "Four legs good, two legs bad" - it's true because it's true, because that's what everyone says.
What LLM is being used?
Curious about potential bias. (Haven't been able to try it yet.) RememberOrwell (talk) 06:30, 27 September 2024 (UTC)
- The extension description states that it uses Llama3-70b Bertaz (talk) 07:44, 27 September 2024 (UTC)
Keep suggestions on the talk page
Articles like Alcaligenes faecalis are not written as a loose collection of every time their subject is mentioned, instead requiring humans to weave reliable sources to comprehensively describe their topic. Using LLMs to assess whether certain statements are represented on the associated articles is an innovative approach, but I caution against posting these suggestions anywhere besides the talk page. Whereas the talk page can be easily archived to resolve spam during breaking news (though I like Aveaoz's idea to have the LLM check against existing talk page proposals), it would be difficult to cleanup if we allow these proposed facts to be posted into the article itself, such as through invisible comments. I think cautioning against unreliable and deprecated sources is sufficient because there are productive ways to use every source. BluePenguin18 🐧 ( 💬 ) 07:08, 27 September 2024 (UTC)
- Thanks, @BluePenguin18! One piece of feedback we've heard is that talk pages aren't the ideal place for article suggestions, because many of them are dormant/unwatched. I agree that letting people add these suggestions directly to the article is risky, but I'm wondering if there could be a more actionable "holding space" than a talk page that doesn't become yet another moderation queue/backlog. What do you think about sending these to the relevant WikiProject's talk page? (Though the same concern as article talk holds, in the sense that many WikiProjects are also pretty dormant, I wonder if this might make it more likely for someone to look at/do something with a suggestion?) What do you think? Do you have other ideas like that, to put these in front of Wikipedians who'd be inclined and excited to do something with good suggestions? Maryana Pinchuk (WMF) (talk) 20:55, 27 September 2024 (UTC)
- First, many articles do not have talk pages sorting them to their WikiProject. Second, many articles have multiple WikiProjects, and if the script posted to all of them, we would to have to mark all the posts as completed after finishing the single task of accepting/declining the proposal. Third, as you note, many WikiProject talk pages are inactive, even in cases where the articles under their purview are regularly edited. Sticking with the A. faecalis example, WikiProject Microbiology's talk page has gone untouched for three months, yet hundreds of articles on microbes are regularly edited each month. I recognize that many editors ignore article talk pages, but personally, I always check them for suggestions before beginning extensive editing. BluePenguin18 🐧 ( 💬 ) 21:30, 27 September 2024 (UTC)
Please enable this for draft space
I tested this against three articles in draft space - Draft:Marshall L. Stephenson, Draft:Murder in New Jersey law, and Draft:William J. Harbison, each using sources and text selections that were clearly on point, and in each case, the tool 1) failed to detect that a relevant draft exists (in the first and third instance, it found nothing; in the second, it found various articles secondarily related to murder in New Jersey); and 2) when prompted with the title of a draft article, found the draft but then spun its wheels endlessly without getting to the step of offering to add a note to the draft talk page. This is frankly a perfect tool for the way I write drafts, it just needs to be able to find them. BD2412 T 12:17, 27 September 2024 (UTC)
- this is really useful feedback. thank you. currently the way it is coded it isn't easy to let it auto-find drafts but adding support for manually tagging drafts it something we could consider doing in the short term. but improving the draft situation overall is a good idea. DErenrich-WMF (talk) 15:42, 27 September 2024 (UTC)
AI, really?
This seems like a terrible idea, AI spits out nothing but garbled false statements. Kirby54 — Preceding undated comment added 13:35, 27 September 2024 (UTC)
- Hey Kirby54, see my reply to MRSC above noting that this AI implementation is just checking whether the claim is documented on the relevant Wikipedia pages. It is not attempting to propose a specific insertion of text into those articles. Thus, an error-prone LLM would not be capable of adding falsehoods to Wikipedia pages in this experiment BluePenguin18 🐧 ( 💬 ) 17:23, 27 September 2024 (UTC)
- Thanks for chiming in here & elsewhere @BluePenguin18 on the question of how AI is being used here. You are correct that we are using AI in this tool only to search Wikipedia and retrieve back some contextual information to the user of the extension (i.e., whether or not there is a relevant article on this topic on Wikipedia – though the user can also just search manually; and whether or not the claim that the user has found/selected is already contained in the article). AI is not involved in writing any text that is posted to the talk page. I'll elaborate on this in the FAQ so hopefully it's less confusing to others! Maryana Pinchuk (WMF) (talk) 21:03, 27 September 2024 (UTC)
Well... where to begin?
- I agree completely with BluePenguin18 above about the genesis and development of articles like Alcaligenes faecalis: it's a really good and concise summary of how WP should and can work. But thousands of less experienced editors really don't get it. As a professor of Mediaeval Literature pointed out to me last year, Wikipedia can be seen as the interface between academia (often dealing with highly technical subjects) and the general public: and such snippets of 'breaking news' detract from the long-term validity of similar articles.
- BTW, Alcaligenes f. has already been edited on this very subject (apparently deliberately ignoring the example in the video) by someone whose edit history and talk page do not inspire confidence, possibly just to get there first. I'm not qualified to judge whether it's a useful edit.
- This "Add a fact" tool works in exactly the opposite manner to the way I (and I suspect many others) actually edit on WP. If I do happen to come across something useful relating to an article I am familiar with, I will open it in the editor, add the relevant info in the article text and make a full cite there and then. Many of the articles I edit depend on scholarly articles, usually via pdfs, which the tool is not capable of addressing.
- The very idea of "Facts" is barely consistent with the fundamental concept of Wikipedia's approach to articles. It could easily be said that there are no facts, only opinions, and WP attempts to balance them using the best of reliable sources.
- Who is actually going to be doing the work once this factoid (cue breathless "Did you know...") has been posted on the talk page? The result, as shown in the video, is incapable of being transferred into the article without further effort from an experienced editor: if it is not simply ignored, someone will have to use their time and effort to give reasons why it's not suitable for inclusion. Only few of these posts could easily lead to exasperation.
- Use of this tool could easily encourage lazy spamming of talk pages by people eager to increase their edit count.
- I find that the use of
|quote=
makes it relatively hard to distinguish the quote from the cite. - I suggest you re-record the video, speaking at approximately half the speed. I know you are very familiar with the tool, having developed it yourself, but as an intelligible introduction to a noob I'm afraid it fails. Your speech comes across as almost garbled. Please take your time.
- The foisting of AI on Wikipedia and Wikimedia has not yet found wide approval. Although there may be positive reasons for using the hallucinatory, imitative mumblings of a village idiot, I for one remain utterly unconvinced. MinorProphet (talk) 14:01, 27 September 2024 (UTC)
- Agree with all statements regarding Wikipedia. Mittzy (talk) 15:08, 27 September 2024 (UTC)
- The "Add a Fact" workflow of proposing statements is obviously very different from how experienced editors approach articles, but I think DErenrich-WMF is reasonably claiming that the act of proposing these facts would serve as a gateway to mainspace editing for new editors. I do not think that this tool would be abused for edit count purposes, simply because there are much easier and more fulfilling ways to boost one's count as a gnome. Regarding AI hallucinations, note that this implementation only uses the LLM to check whether the claim is represented on associated articles. It does not propose a particular text insertion to the talk page. BluePenguin18 🐧 ( 💬 ) 18:22, 27 September 2024 (UTC)
- Thanks for clearing these points up. MinorProphet (talk) 22:49, 27 September 2024 (UTC)
Does it, or does it not, work with Firefox?
The description of the tool states, "Add A Fact is available for the Google Chrome and Mozilla Firefox browsers." And there is a comment (above) which says, "Yeah we targeted Firefox and Chrome first because of their wide use in the community".
So in installed it in Firefox. It seemed to install OK, but I couldn't get it to work. So I delved into the docs, and I found this statement in the FAQ: "For technical reasons the extension will not just work on Firefox due to some manifest 3 API's that Firefox doesn't support".
If it is not supported in Firefox, I would understand that. I am aware of the issues of browser compatibility. And I congratulate you on what you have achieved so far. But can you perhaps amend the information to clarify this point. (And if it is not supported by Firefox, perhaps it should be removed from the FF add-ons page? Mike Marchmont (talk) 16:35, 27 September 2024 (UTC)
- I'm running Firefox 130.0.0 and it's working for me. Which version do you have installed? Tod Robbins (talk) 16:45, 27 September 2024 (UTC)
- I just tried it in Firefox and it worked for me (see screenshot). Could you tell us more about your setup so we can investigate why it's broken for you? DErenrich-WMF (talk) 21:33, 27 September 2024 (UTC)
- OK, I'm running FF 127.0. Not the latest version, but close. This is what I did:
- * Installed the extension in FFF.
- * Opened it in the sidebar.
- * Higlighted a passage in a web page.
- This is how it looks:
- I'm now at the point where it says "run the extension". But how to do that? I can't see a button or a menu option or anything else that will allow me to run it.
- (I hope the screen shot is clear.)
- (By the way, I have enabled all permissions for the extension.)
- Mike Marchmont (talk) 15:09, 28 September 2024 (UTC)
- It should autorun when you select text with the sidebar open. If that doesn't work, try closing the sidebar, selecting some text and clicking on the extension icon. If the sidebar reopens with the instruction (like in your screenshot) select some other text.
- For me the extension only works after I select some text while the sidebar is open. If I select the text before opening it, the extension is unable to grab the selected text. Bertaz (talk) 21:34, 28 September 2024 (UTC)
- Mike Marchmont (talk) 15:09, 28 September 2024 (UTC)
Please explain the required permissions
So I said to myself, why not give it a try, and followed the link to the Firefox Add-Ons store. Lo and behold, the extension wants to be able to read all the data on all websites. Which, of course, includes anything entered on a form on any website, including usernames, passwords, bank card numbers, CVV2 numbers, and so on. Of course, I politely declined the installation of the extension. The required permissions and why they are needed would be most welcome, as would be an official statement from the Wikimedia Foundation regarding the collection and use of data. Imerologul Valah (talk) 21:17, 27 September 2024 (UTC)
- @Imerologul: This is a really good question and I knew this would be problematic for some. We requested that permissions because we need to be able to tell what text you have selected. To do that we need to be able to run javascript in the context of the page (which can be any page). If I'm mistaken and there's a way to get around this we'd definitely want to do it that way. If it's any consolation the code is open source and it should be easy to check it isn't malicious and build it yourself. DErenrich-WMF (talk) 21:30, 27 September 2024 (UTC)
- @DErenrich-WMF: What I was trying to say is that the need for powerful permissions should be highlighted on the extension's home page in the Add-Ons store, with an explanation of why they are needed. And an official statement from Wikimedia Foundation saying that no personal data will ever be collected and the extension will never be sold to shady actors would be most welcome, because developers change, they move to other projects, and generally stuff happens during the lifetime of a piece of software. Imerologul Valah (talk) 20:04, 28 September 2024 (UTC)
- I agree that an explanation of the permissions would be good. But a statement won't prevent personal data collection. If for whatever reason the maintainers of the extension decide to start collecting data, they can do so even leaving the statement up. The best way to avoid any of these scenarios is by keeping the extension open source. So that anyone can check what the extension actually does.
- Also the permission "Access your data for all websites" is needed to use the selected text from any website the user browses. Even if a user preferred manually selecting in advance each website, this is not possible on Firefox. See [3][4]
- @DErenrich-WMF: Wouldn't dropping "https://*/*" in "host_permissions" lose no functionality, as it's declaring "activeTab" permission? Maybe there's some technical limitation I'm not considering. Because just "activeTab" won't trigger the "[…]all websites" permission. Bertaz (talk) 23:07, 28 September 2024 (UTC)
- Thanks for the suggestion. I'll take a look at this this week. I do know we had internal conversations when we needed to increase the permissions and thought there was no workaround. This was a while ago so I may have explained it incorrectly and we may have been wrong.
- I'm not a lawyer but it is my understanding that the privacy policy covering data collected by this extension follows the same rules as that used on Wikipedia. DErenrich-WMF (talk) 05:08, 29 September 2024 (UTC)
- @DErenrich-WMF: What I was trying to say is that the need for powerful permissions should be highlighted on the extension's home page in the Add-Ons store, with an explanation of why they are needed. And an official statement from Wikimedia Foundation saying that no personal data will ever be collected and the extension will never be sold to shady actors would be most welcome, because developers change, they move to other projects, and generally stuff happens during the lifetime of a piece of software. Imerologul Valah (talk) 20:04, 28 September 2024 (UTC)
Why are we trying to (1) Use AI; (2) Encourage editing off-site; (3) Risk flooding of mainspace with drive-by gunk?
Inquiring minds want to know. Looks on the face of it like another terrible idea from the bureaucracy. Carrite (talk) 22:48, 27 September 2024 (UTC)
- First, AI is only being used to analyze whether the highlighted statement is represented on associated Wikipedia pages. Second, I think that using this off-site extension could ultimately be a gateway to on-site editing by having novices see how editors act on their talk page proposals. Third, regarding drive-by posting, I am in agreement that the tool should scan whether the talk page already has a pitch to add the proposed fact BluePenguin18 🐧 ( 💬 ) 00:43, 28 September 2024 (UTC)
- As I pointed out earlier, the term "fact", proposed or otherwise, has no place on WP, which is not Speakers' Corner. ;) MinorProphet (talk) 15:34, 28 September 2024 (UTC)
Doubtful about the fundamental premise of a tool like this
Thanks for experimenting with this tool, I appreciate the time and effort invested. However, I believe tools like this are fundamentally flawed from the outset. My reasons are as follows:
- Everyone agrees that an LLM writing any articles is a terrible idea, so the best it can do is leave little notes in the suggestions box, which is what this extension does essentially.
- However, the difficult part of writing Wikipedia is not finding random titbits of information; it is integrating them into the text of all the relevant articles (of which there might be many), checking the sources, establishing their credibility, ensuring articles aren't obviously contradicting each other, and that they don't have repeated and/or contradictory claims internally resulting from many independent edits. Those are all tasks for a subject matter expert, or at least a dedicated layman who can invest the time in gaining enough insight in a given field to be able to contribute. This tool helps with none of that.
- Thus, we now have a tool that does not help with any of the hard parts, and automates the easy part. The best this can result in is a huge backlog of suggestions that will be ignored by human editors as essentially equivalent to spam; at worst this will drown out actual meaningful discussions on talk pages and potentially create a dangerous precedent amongst less experienced users who might believe that those are things that should be added to articles and aren't merely suggestions to be carefully vetted.
- Lastly, I strongly object to the use of "facts" in the description of this extension. Those are, at best, claims, and random places on the Internet do not necessarily contain any facts, so calling them that is actively harmful to the critical thinking we're trying to cultivate, IMHO.
In other words, as with many other "AI" applications, this is a tool that doesn't what would be actually useful, but rather it does what LLMs can achieve easily. I don't think shoehorning this into the editorial process, or even suggesting to users that it is potentially a good idea is wise.
If you want to make a tool where an LLM could genuinely make the process easier, how about a tool that tries to detect repetitions and/or contradictions in articles? A little summary of "these paragraphs seem redundant", where I can click and jump to the relevant place in the article and see it in context easily would be very useful. Bonus points if it could figure out which articles are related and either repeat the same information instead of referring to a main article, or contradict it. This is an extremely widespread problem affecting many articles and one that is very tedious to deal with manually. mathrick (talk) 02:06, 28 September 2024 (UTC)
- I just want to drop in and say that this tool is perfect for an editor like me, because I do enjoy the integrative part, and am able to do that better and faster with a tool that drops in the quote and the cite. I may be an outlier in that regard, but there are some of us who do this. In practice, however, I am not going to use it to find the right article for the information so much as to put the information where I already know it should go. BD2412 T 02:30, 28 September 2024 (UTC)
Comment by Imerologul
Please note that, at least on Firefox, this extension requires the permission to read all the data you enter on any web page, including usernames and passwords. Imerologul Valah (talk) 21:07, 27 September 2024 (UTC)
- This comment was originally posted on User:DErenrich-WMF/Add_A_Fact_Experiment and I moved it to here. --SCP-2000 04:34, 28 September 2024 (UTC)
How about a tool to check sources for problematic statements in Wikipedia?
"Add A Fact" is a great tool, but how about making a tool the other way around? I mean, highlight a "citation needed" statement in Wikipedia and help me find sources for them. I would prioritize fixing existing problematic statements rather than adding more factual statements. The article will be more reliable and verifiable after fixing "citation needed" statements. --Jojit (talk) 06:24, 28 September 2024 (UTC)
- How about entire problematical _articles_ in Wikipedia? I give you Talk:Ali James, which I came across yesterday and which I feel represents the underlying cracks in the very foundations of WP, much as there are cracks in the foundations of mathematics: but no-one wants to talk about them, even less fix them. Am I becoming a Deletionist? Plenty of my earlier articles do not bear scrutiny. How about a moratorium on all new articles, and edits to all existing ones, except to fix these egregious errors? MinorProphet (talk) 19:46, 28 September 2024 (UTC)
- We've considered experimenting with tools that do exactly. It may be something we investigate in the future. DErenrich-WMF (talk) 04:57, 29 September 2024 (UTC)
What the tool appears to be trying to achieve
As far as I can ascertain from the main page ("we want more excited editors!" - a slight paraphrase), this tool is hoping to encourage non-wikipedians and other beginners to contribute to the encyclopedia. I just don't think it's a good way. 'Excited editors' is exactly what we don't want: we would like level-headed, intellectually curious, emotionally robust people capable of identifying dross from worthwhile information, circumscribed by a vast nebulous bureaucracy of rules, advice, manuals, essays, admins and the dreaded Arbcom. Should we not be spending our time wondering how to attract more editors capable of coping with this? Once you get drawn in to contributing to WP, the learning curve turns out to be exceptionally steep, and then there's the inter-personal element which is possibly the hardest barrier to overcome. Just a thought. MinorProphet (talk) 15:56, 28 September 2024 (UTC)
- Thanks for your comments. This isn't my area of expertise but it's my understanding that a lot of the efforts around trying to attract new users are about finding small well-defined low-risk tasks that they can do (e.g. suggested edits). Flagging information that's maybe missing from the Wikipedia could maybe be such a task. DErenrich-WMF (talk) 05:03, 29 September 2024 (UTC)
Why not have an option to add the information directly as a new edit rather than posted on the talk page?
Yes I'm asking the question on the title. By the way, I can see this helping editors of under-updated articles such as those about Kuwait, where I live. FSlolhehe (talk) 19:21, 28 September 2024 (UTC)
- Yup that's something we have considered and maybe future work would do something like that. The team had vigorous conversations about how or whether we should drop the user into an editor to make the edit immediately. The main reason we didn't go that route for now is that making the edit can be complicated and we want this tool to be easy to use for relatively new users. DErenrich-WMF (talk) 04:56, 29 September 2024 (UTC)
- You are then offloading the work to people who have that page on their watch list. If you are already autogenerating the citation, then let users copy that and manually edit the article. Please don't enable this tool in this current configuration and don't advertise it! Matthias M. (talk) 17:32, 29 September 2024 (UTC)