Wikipedia talk:WikiProject Edit requests
Add topic| This is not the place to request edits. If you'd like to make an edit request, please visit the edit request wizard. |
| This is the talk page for discussing WikiProject Edit requests and anything related to its purposes and tasks. |
|
| Archives: 1Auto-archiving period: 12 months |
| This project page does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||
| ||||||||
Listing of Fascist countries
[edit]Why, would anyone donate a single dime to your site. It is full of untruths, left winged rhetoric designed to create violence in our society. Listing the United States of America as a nation of fascism is absurd. Change this ASAP, democracy is what should be listed, that is the truth. Trumpism??Really??? If Trump were really a fascist dictator he would shut your site down and jail anyone connected to it. IDIOTS! 2601:1C0:4302:9FB0:267F:D854:ED3D:C522 (talk) 04:50, 20 September 2025 (UTC)
Suresh Chatwal,actor, biography, wife of Suresh Chatwal
[edit]Name of Suresh Chatwal's wife isUsha Suresh Chatwal and NOT Priya Sachdev. Not expected of wikipedia to give such wrong and misleafing information. 202.134.174.101 (talk) 14:43, 31 October 2025 (UTC)
- Hi IP editor, please open an edit request on the page in question using the edit request wizard. Thanks, Encoded Talk 💬 09:21, 3 January 2026 (UTC)
Fred Brown(Former American Basketball Player)
[edit]I would like to respectfully clarify a recurring issue regarding the draft for Fred "Disco" Brown (born 1962). The draft continues to be declined under the assumption that a page already exists for him-specifically referring to Fred Brown (born 1948), also known as Downtown Freddie Brown of the Seattle SuperSonics. While the two individuals share a similar name and both were drafted into the NBA and both have played at Rucker Park, they are not the same person. Their lives, careers, achievements, and public records are entirely separate. Key points of distinction include Fred "Disco" Brown born 1962, a native New Yorker with a documented 4-decade impact on New York basketball and its street basketball community as well. The other Fred Brown born 1948 raised and developed primarily outside New York and known exclusively for his NBA career. Fred "Disco" Brown appears in the verified 1983 Phoenix Suns NBA draft Photograph, which clearly shows he is not the same individual born in 1948 of the Seattle SuperSonics. The age, appearance, and historical context make the distinction unmistakable. Fred "Disco" Brown has documented honors, records, and awards from his time at Virginia Commonwealth University (VCU) and selection to the Interworld All-Star Basketball Tour of Asia (1984). A Team of consisting of former NBA players some former All-Stars, who later became NBA Hall of Famers, and some named to the 50 greatest players of all time now 75. An honorable distinction for Pro rookie prospect reflecting his talent and potential.
Although both individuals played at Rucker Park it was in different eras and Fred "Disco" Brown's relationship with Rucker Park is entirely different and extensively verified. Over 4 decades of involvement, documented in news media, newspapers, video interviews, event footage and community archives. Recognized as a Pro Rucker Hall of Famer (inducted 2007) and Entertainers Basketball Classic (EBC) Hall of Famer (inducted 2021) and longstanding mentor, organizer, and youth advocate whose presence is interwoven with the park's modern history. Collaborating with Bob McCullough/Fred Crawford (Pro Rucker), Greg Marius, Gusto (Entertainers Basketball Classic (EBC).
Fred "Disco" Brown (Former American Basketball Player) draft is supported entirely by public records of honors, awards, achievements and professional engagements. Newspaper coverage, third-party media features, verified photographic and video sources, event documentation These sources represent a career and legacy that are distinct and notable on their own, separate from Fred Brown the NBA player born in 1948.
I fully respect and follow Wikipedia's policies on notability, verifiability, and the biographies of a person's guidelines. My request is simple that this draft be evaluated based on its own independently verified content rather than being conflated with another individual who shares a similar name. If any procedural action is required, such as renaming the draft, merging duplicates, or applying a disambiguation title, I am more than willing to follow the correct steps.
Thank you again for your time, attention, and guidance. I appreciate the help in ensuring the draft can and is reviewed accurately as a biography of a different and notable individual.
Monjaz (talk) 19:30, 18 November 2025 (UTC)
- Hi @Monjaz, if this is referring to Draft:Fred Brown (basketball, born 1962), it was declined due to the use of LLM-generated content. If it's not, and the issue has not yet been resolved, please let me know. Thanks, Encoded Talk 💬 20:16, 28 December 2025 (UTC)
Hello, I would like to make a request for a proof read or a Wikipedia check of quality for the gyaru article. I added some information yesterday but no one has reverted or made an issue with my edits but I find them needing some clearance or if they are vaild or valuable edits to Wikipedia. Thank you. ~2025-39711-02 (talk) 22:02, 10 December 2025 (UTC)
Add a Suggestion for Editors
[edit]I answer a lot of edit requests, and the main reason I pass on some of them is due to their length. Requests trying to change multiple paragraphs at once or replace the page entirely are common, especially in the COI queue. I know we already have some guidance on conciseness, but I think it's worth making that more prominent, both on the relevant pages and on the wizard. What do y'all think? InfernoHues (talk) 00:07, 5 April 2026 (UTC)
Discussion about the redirect "Template:Edit fully protected"
[edit]Please join the discussion at Template talk:Edit fully-protected#Redirect Template:Edit fully protected → Template:Edit protected or Template:Edit fully-protected. —andrybak (talk) 21:31, 3 May 2026 (UTC)
COIREQ backlog
[edit]There is currently a large backlog of 1,648 unanswered COI edit requests in Category:Wikipedia conflict of interest edit requests. Following a post on COIN yesterday, we've managed to reduce it quite a bit. Your assistance would be appreciated. MediaKyle (talk) 11:14, 4 May 2026 (UTC)
Proposal: Browsable COI edit request queue
[edit]Hi editors! Last year, the firm I work at, Beutler Ink, proposed updates to Template:Edit COI. The updates, which added the "request summary," "request status," and "under review" fields to make the edit request queue more user-friendly, were well-received and implemented by the volunteer editing community. Now, I'm here to propose a related improvement: a browsable page that transcludes all open COI edit requests into one place.
Currently, User:AnomieBOT/COIREQTable lists all open requests as a list of links with limited information about the requests. Even as improved last year, an editor still must click to the request to see exactly what's being requested. The edit request queue has been hovering around 500 requests, which highlights the need to continue to improve this process for reviewers. After some brainstorming, we developed the concept of the browsable COI queue. However, the more technical side of Wikipedia is not our expertise, so we once again worked with User:Bawolff, who has the deep coding knowledge needed to create a proof of concept in their userspace. Now, we would like to share the tool with the volunteer editing community for feedback.
Bawolff created several different versions, which you can see listed here, but I recommend editors take a look at the following two versions:
This tool transcludes specific edit requests from each article's Talk page in a paginated and browsable format. It supports both chronological and alphabetical sorting.
A few notes on the this tool:
- MediaWiki's transclusion size limits the practical page size at around 10–15 requests per page.
- This does not replace COIREQTable. It is a companion tool designed to make the queue visually easier to work through.
- Bawolff says that while this proposed tool currently lives in userspace, it can be moved into Wikipedia namespace, if desired.
Let us know what you think! The goal here is to have a tool that makes the COI queue a bit more like a noticeboard. This could make it easier for reviewing editors to locate specific requests that are of interest to them and cut down on the amount of clicking back and forth between the queue and article Talk pages.
Danilo Two (talk) 13:10, 14 May 2026 (UTC)
- @Encoded, Jenny8lee, Primefac, Terasail, AlphaBetaGamma, Chaotic Enby, Anomie, and Sohom Datta: You all commented on a previous proposal by Beutler Ink to improve the edit COI process, so I'm pinging you here for feedback on whether a browsable COI edit request queue would be helpful. If you're interested, I'm curious what you think. Danilo Two (talk) 19:58, 25 June 2026 (UTC)
- This looks pretty neat, I like it! Only issue, in "Oldest to newest, 15 per page", the first one returns an error: Talk page cannot be included because it exceeds limits. Please visit the original talk page. Chaotic Enby (in solidarity · talk · contribs) 10:32, 26 June 2026 (UTC)
- Thanks! I've made note of this feedback. Let me know if there's anything else you think we should work on with it. Danilo Two (talk) 20:09, 26 June 2026 (UTC)
- it skips any page that surpassesses the post expand include size limit, because transcluding those tend to break the whole page. Bawolff (talk) 21:28, 26 June 2026 (UTC)
- This looks pretty neat, I like it! Only issue, in "Oldest to newest, 15 per page", the first one returns an error: Talk page cannot be included because it exceeds limits. Please visit the original talk page. Chaotic Enby (in solidarity · talk · contribs) 10:32, 26 June 2026 (UTC)
- @Encoded, Jenny8lee, Primefac, Terasail, AlphaBetaGamma, Chaotic Enby, Anomie, and Sohom Datta: You all commented on a previous proposal by Beutler Ink to improve the edit COI process, so I'm pinging you here for feedback on whether a browsable COI edit request queue would be helpful. If you're interested, I'm curious what you think. Danilo Two (talk) 19:58, 25 June 2026 (UTC)
{{Edit protected}} and WP:Edit filter
[edit]There should be a request level added to Template:Edit protected (edit | talk | history | links | watch | logs) to handle edits disallowed by WP:Edit filters, that are still good edits. This would reduce the load on WP:EFFP processors for edits that merely need elevated user access levels (like curse words), or for which an IP-range is being filtered out. Instead of all anonymous users in a particular address block flooding EFFP for edits. Such as {{Edit protected|level=editfilter}} -- ~2026-25149-07 (talk) 03:55, 30 May 2026 (UTC)
- I think a level for edit filters might be too specific. The folks at WP:EFFPR seem to act on reports as a form of edit request, so there's no need to overlap. From what I can see, a number of your false-positive reports were implemented. Also, the filters might be less eager if you create an account.
- I think this brings up an unfortunate quirk of the template, though: I think a generic, uncategorized level would be an appropriate default for {{Edit protected}} instead of semi-protected; it would indicate requests in need of triage since many requests erroneously (and unintentionally) end up in the semi-protected category (usually COI requests). I'm not a template editor, though...
- Anyways, I recommend you keep sending your requests to WP:EFFPR instead of using ordinary edit requests. Kodning 🌸 (talk) 19:24, 31 May 2026 (UTC)
Discussion at Wikipedia talk:Edit requests § Separate response templates
[edit]
You are invited to join the discussion at Wikipedia talk:Edit requests § Separate response templates. Kodning 🌸 (talk) 00:37, 3 June 2026 (UTC)
How can I refresh the bot?
[edit]I use the page User:AnomieBOT/COIREQTable to know what's waiting. I notice that sometimes it seems like it's stale. Is there a way I can trigger a rerun, or a schedule I should know about? Packrat3860 (talk) 00:56, 22 October 2026 (UTC)
- Bots and many other automated tools are currently down due to WP:PHP2026 (the security crisis that's impacting many websites). —ClaudineChionh (she/her · talk · email) 01:35, 22 October 2026 (UTC)
COI Backlog Drive - What is needed?
[edit]There was discussion at WP:AN about the backlog getting a bit out of hand, with several folks suggesting a backlog drive might be a good way to get it under control. I'm not terribly familiar with backlog drives but I like the idea and I'd like to try to get the ball rolling. I'm proposing the below as a rough structure to work off of. Very open to suggestions but I'd like to avoid making the perfect the enemy of the good so that we can maybe get it up and running for December or January. I've roughly modeled this off of the WP:GOCE backlog drive cause I participated in that one and it was fun.
---
Instructions: We have a sign up page where you can add your name and get a little subsection. When you're taking a request mark it as {{edit COI|U}} and put it in your "in progress" field. When you're finished, mark the request as accepted, rejected, or partially accepted (see {{edit COI}}) and put it in the "done" field. For actually doing the requests we can point people at WP:COIRESPONSE.
Rewards: Maybe have a couple tiers of rewards plus one for the most? A minor barnstar if you do 3, a regular barnstar if you do 15, something special if you're at the top of the leaderboard? I don't know what the going rate on a barnstar is, but it seems pretty subjective. I think it's probably most important that we make that first rung reachable for someone who's never done it before.
Oversight: GOCE has reviewers that look at both requested reviews (essentially asking someone to take a second look) and a random selection of the submissions. If someone is truly gaming the system or otherwise not being constructive we can warn them and/or revoke their "credit". I think we also probably want to discourage folks from taking more than one request in progress at a time to avoid parking on open requests, but I doubt it will be a frequent enough problem that we need a strict policy.
Advertising: I know even less about this than the other parts. It's possible to have this show up as suggested to people in the same way other drives are. I don't know who we have to ask for that. I presume they would need some lead time.
---
Do we think something like this is feasible? Can we start getting a sign up of folks who would like to help put it together? Is there anything really important about how a drive needs to work that I've missed here? Feedback and/or co-conspirators would be most welcome. Packrat3860 (talk) 14:32, 27 October 2026 (UTC)
- Also if this is already being discussed in detail elsewhere, let me know and I'll go there instead of splitting our efforts ^~^ Packrat3860 (talk) 14:34, 27 October 2026 (UTC)
- I would support a backlog drive, as that seems like the only way for us to feasibly get the backlog down. Theeverywhereperson talk here In solidarity! 15:05, 27 October 2026 (UTC)
- Pinging @Czarking0, who mentioned a backlog drive on the category talk page a while back. Also, I'd be down to help with a drive. MetalBreaksAndBends (One for all) 15:47, 27 October 2026 (UTC)
- I have thrown up a page for a backlog drive that people can use to work if they want. Also threw up a tab on the main page of the WikiProject that leads to various useful things, and some counters for how many open edit requests there are. I'm assuming there is essentially no resistance to being bold with the project pages here, as the WikiProject has not been particularly active recently. I remember someone saying something about a tutorial for responding to COI edit requests, if that has been made and someone has the link to it that would be appreciated.
- If people would like me to I can make a full backlog drive page. None of it would be final, I'm mainly thinking about it in terms of giving people something more tangible to work with and make changes to. –Maltazarian ᚾparleyinvestigateᛅ 16:35, 28 October 2026 (UTC)
- I think boldness is called for here, thanks. The only thing I would suggest is to maybe put some indicator on the page that this is a work in progress so we haven't "started" the drive yet (since I assume we'll want to have some time period for it?). But yes, thanks for putting that together and if I have time later I might go add some (draft) structure to it. Packrat3860 (talk) 17:05, 28 October 2026 (UTC)
- Where is the page anyway, for one, and I would like to be on the 'board' of people regulating this drive (organisers), maybe it would be myself, Maltazarian and Packrat 3860? someone also has to request mass message delivering rights, and this drive could and should go for >1 month to get the backlog down to a reasonable level. We can use that page to discuss. Theeverywhereperson talk here In solidarity! 17:07, 28 October 2026 (UTC)
- Page is here Wikipedia:WikiProject_Edit_requests/Planned_late_2026–early_2027_backlog_drive (for now) Packrat3860 (talk) 17:09, 28 October 2026 (UTC)
- Honestly, Packrat3860's suggestion is the best for what we're trying to do here. However, I will have to say that the things we need to sort out for this to work are:
- Working on the page about the backlog drive
- Sorting out prizes for how well you do (with a separate leaderboard for drive participants only so that she [Packrat3860, who is currently top of the leaderboard for most COI requests answered] doesn't give the prize to herself)
- The timeframe, and whether or not the recruitment phase overlaps with the participation phase (and if people can join at anytime during the event)
- How we let people know (we'll have a watchlist notification, and all of us get event coordinator rights and one of us is in charge of mass-message sending to everyone's talk page) and who we tell. Theeverywhereperson talk here In solidarity! 17:17, 28 October 2026 (UTC)
- There's a user tutorial I found useful at User:Rusalkii/Responding to COI edit requests (was mentioned at the AN posting). Backlog drives typically don't go for longer than a month at a time, I believe, as this can lead to people feeling overwhelmed and/or interest petering out. I'd also definitely encourage people to join at any time, the more hands helping the better. Perfect4th (talk) 03:55, 29 October 2026 (UTC)
- That was the tutorial I was looking for! Thanks!
- Some edit drives have lasted for two months, such as Wikipedia:New pages patrol/Backlog drives/January–February 2026, but I don't know if that would be a good idea here. I will ask people more familiar with organizing these kinds of things.
- I agree we could use more help, could especially use some advice from experienced organizers. I will ask at WP:VPM or something like that.
- I have created some new barnstars as awards for the drive and a special medal for the winner. Got some other ideas too, which can be seen at the backlog drive page. Still iffy on what the best way to do scoring is. There should be some way of rewarding more complicated reviews or else people will selectively go for the easy edit requests. –Maltazarian ᚾparleyinvestigateᛅ 22:43, 30 October 2026 (UTC)
- The usual at AfC is more points for older reviews, since those are usually harder. Rusalkii (talk) 00:23, 31 October 2026 (UTC)
- That was one of the things I considered. I was torn between having a separate award for doing old requests and giving extra points for it. Doing both is always an option. –Maltazarian ᚾparleyinvestigateᛅ 00:50, 31 October 2026 (UTC)
- I think December 2026-January 2027 with signups throughout the competition would be the best here. Theeverywhereperson talk here In solidarity! 05:00, 31 October 2026 (UTC)
- Those months are indeed the ones I have in mind. There is little else scheduled in December and January, and we obviously want to do this sooner rather than later to get the backlog back down to normal levels. –Maltazarian ᚾparleyinvestigateᛅ 05:37, 31 October 2026 (UTC)
- Now that we've got the dates, I feel like we should start an organisation commitee with me, you and Packrat3860 to iron out the finer details of this drive. Theeverywhereperson talk here In solidarity! 05:39, 31 October 2026 (UTC)
- (repinging everyone due to lack of progress) The backlog is only increasing at a blistering speed. Therefore, I'll ping everyone because we need to have the drive ready and ways to tell everyone now. Packrat3860 Rusalkii Maltazarian MBAB. Sorry about the pings, but discussion is practically required as the backlog is at 1400. Theeverywhereperson talk here In solidarity! 13:29, 4 November 2026 (UTC)
- I'm happy enough to put my name on the committee but I'm not sure what is next to be done. Should we have an RFC to ratify the format? Is there someplace we can request the permission to advertise this drive on wiki? Packrat3860 (talk) 14:07, 4 November 2026 (UTC)
- Definitely an RfC, but the best thing I can think of is getting a banner at the top of every page and watchlist notifications in order to get the largest amount of people. Theeverywhereperson talk here In solidarity! 14:40, 4 November 2026 (UTC)
- I don't know how to get a banner or watchlist notifications. I'll try to get the proposed "rules" of the drive complete by sometime this weekend and then we can open an RFC? I think it'd be nice to aim for a drive in December if we can, and that should leave us enough time. Although we haven't really heard from a ton of people yet, and I don't want to rush into it with only a very small group having approved the idea. Even if the queue is long there is still no WP:DEADLINE. Packrat3860 (talk) 22:55, 4 November 2026 (UTC)
- Re watchlist notifications, Wikipedia:Watchlist notices seems to indicate just post a notice at the MediaWiki talk page listed there, though that's probably best to wait until you have details largely worked out to get consensus easiest. Where do you have in mind for the RFC? Perfect4th (talk) 03:10, 5 November 2026 (UTC)
- Ok yeah that looks pretty straightforward. As for the RFC I figured I could open one here on this talk page (although I'd make a new thread as this one is getting pretty deeply nested. Packrat3860 (talk) 04:29, 5 November 2026 (UTC)
- Re watchlist notifications, Wikipedia:Watchlist notices seems to indicate just post a notice at the MediaWiki talk page listed there, though that's probably best to wait until you have details largely worked out to get consensus easiest. Where do you have in mind for the RFC? Perfect4th (talk) 03:10, 5 November 2026 (UTC)
- I don't know how to get a banner or watchlist notifications. I'll try to get the proposed "rules" of the drive complete by sometime this weekend and then we can open an RFC? I think it'd be nice to aim for a drive in December if we can, and that should leave us enough time. Although we haven't really heard from a ton of people yet, and I don't want to rush into it with only a very small group having approved the idea. Even if the queue is long there is still no WP:DEADLINE. Packrat3860 (talk) 22:55, 4 November 2026 (UTC)
- Definitely an RfC, but the best thing I can think of is getting a banner at the top of every page and watchlist notifications in order to get the largest amount of people. Theeverywhereperson talk here In solidarity! 14:40, 4 November 2026 (UTC)
- I don't have the time now to organize a drive, sorry :(. Ping me if you want tech or admin support but I'm probably mostly sitting this one out. Rusalkii (talk) 16:43, 4 November 2026 (UTC)
- I'm happy enough to put my name on the committee but I'm not sure what is next to be done. Should we have an RFC to ratify the format? Is there someplace we can request the permission to advertise this drive on wiki? Packrat3860 (talk) 14:07, 4 November 2026 (UTC)
- (repinging everyone due to lack of progress) The backlog is only increasing at a blistering speed. Therefore, I'll ping everyone because we need to have the drive ready and ways to tell everyone now. Packrat3860 Rusalkii Maltazarian MBAB. Sorry about the pings, but discussion is practically required as the backlog is at 1400. Theeverywhereperson talk here In solidarity! 13:29, 4 November 2026 (UTC)
- Now that we've got the dates, I feel like we should start an organisation commitee with me, you and Packrat3860 to iron out the finer details of this drive. Theeverywhereperson talk here In solidarity! 05:39, 31 October 2026 (UTC)
- Those months are indeed the ones I have in mind. There is little else scheduled in December and January, and we obviously want to do this sooner rather than later to get the backlog back down to normal levels. –Maltazarian ᚾparleyinvestigateᛅ 05:37, 31 October 2026 (UTC)
- I think December 2026-January 2027 with signups throughout the competition would be the best here. Theeverywhereperson talk here In solidarity! 05:00, 31 October 2026 (UTC)
- That was one of the things I considered. I was torn between having a separate award for doing old requests and giving extra points for it. Doing both is always an option. –Maltazarian ᚾparleyinvestigateᛅ 00:50, 31 October 2026 (UTC)
- The usual at AfC is more points for older reviews, since those are usually harder. Rusalkii (talk) 00:23, 31 October 2026 (UTC)
- Honestly, Packrat3860's suggestion is the best for what we're trying to do here. However, I will have to say that the things we need to sort out for this to work are:
- Page is here Wikipedia:WikiProject_Edit_requests/Planned_late_2026–early_2027_backlog_drive (for now) Packrat3860 (talk) 17:09, 28 October 2026 (UTC)
- Where is the page anyway, for one, and I would like to be on the 'board' of people regulating this drive (organisers), maybe it would be myself, Maltazarian and Packrat 3860? someone also has to request mass message delivering rights, and this drive could and should go for >1 month to get the backlog down to a reasonable level. We can use that page to discuss. Theeverywhereperson talk here In solidarity! 17:07, 28 October 2026 (UTC)
- I think boldness is called for here, thanks. The only thing I would suggest is to maybe put some indicator on the page that this is a work in progress so we haven't "started" the drive yet (since I assume we'll want to have some time period for it?). But yes, thanks for putting that together and if I have time later I might go add some (draft) structure to it. Packrat3860 (talk) 17:05, 28 October 2026 (UTC)
- I made a template for signups: User:Packrat3860/coi_drive_signup. Apologies if there's already something for this I should have used instead, but it should let people sign up with a one line subst. Feel free to edit it to suit whatever we come up with as far as scoring. Packrat3860 (talk) 00:31, 31 October 2026 (UTC)
- I have tried to flesh out the proposal for the drive. There's still a couple segments marked TODO. Notably, I know there are some scripts/tools for assisting with COI edit requests but I don't use them so I don't really know where to point people. I have also made some changes to the scoring as proposed by @Maltazarian:. I think the idea of awarding more points for old requests or request involving a lot of references to check is good, but I wanted to simplify the scorekeeping a bit just so that people aren't turned off by the complexity of the bookkeeping. Very open to input on that. I've got my signup template working fairly well now with an example in there. If people could review and let me know if there's anything big that needs reworking before we move on to an RFC that'd be awesome. Packrat3860 (talk) 18:32, 7 November 2026 (UTC)
I know there are some scripts/tools for assisting with COI edit requests but I don't use them so I don't really know where to point people.
- I think you're looking for User:Terasail/COI Request Tool. crtbob@talk:~$ ls contribs 19:04, 7 November 2026 (UTC)
- Added, thanks. Packrat3860 (talk) 19:55, 9 November 2026 (UTC)
- Packrat3860 Maltazarian It would be nice if we had it December-2026 to January 2027, I just pinged you to get your opinions. Signup opens 25 November, and Rusalkii is it possible for you to design a banner/ that thing that shows up at the top, then publish it when signups start? Theeverywhereperson talk here In solidarity! 04:34, 11 November 2026 (UTC)
- I've never done that before and I'm not familiar with the process. Do you mean a watchlist notice? Rusalkii (talk) 04:43, 11 November 2026 (UTC)
- We can do a watchlist notice but I also wanted that banner that shows at the top of pages when things are happening. I don't know what it's called. Theeverywhereperson talk here In solidarity! 07:01, 11 November 2026 (UTC)
- Can you take a screenshot of one or something? I also don't really know what you're talking about. Packrat3860 (talk) 07:02, 11 November 2026 (UTC)
- Finally found something like it at meta:CentralNotice, and can I move the page to 'planned December 2026-January 2027 COI backlog drive'? Theeverywhereperson talk here In solidarity! 09:31, 11 November 2026 (UTC)
- Oh, the event banner thingy. I don't think they usually do those for backlog drives? Rusalkii (talk) 17:35, 11 November 2026 (UTC)
- It would probably be a good idea to get some more eyes on this, since I don't think anyone here has experience in organizing a backlog drive. Should we post this to one of the VPs? MetalBreaksAndBends (One for all) 17:45, 11 November 2026 (UTC)
- Definitely interested in getting some wider input on it, especially from anybody with experience running an "event" on wiki. I don't want to wait around too long, but I also don't want to rush into something that it seems like not very many people have looked at. Packrat3860 (talk) 06:34, 12 November 2026 (UTC)
- It would probably be a good idea to get some more eyes on this, since I don't think anyone here has experience in organizing a backlog drive. Should we post this to one of the VPs? MetalBreaksAndBends (One for all) 17:45, 11 November 2026 (UTC)
- Oh, the event banner thingy. I don't think they usually do those for backlog drives? Rusalkii (talk) 17:35, 11 November 2026 (UTC)
- Finally found something like it at meta:CentralNotice, and can I move the page to 'planned December 2026-January 2027 COI backlog drive'? Theeverywhereperson talk here In solidarity! 09:31, 11 November 2026 (UTC)
- Can you take a screenshot of one or something? I also don't really know what you're talking about. Packrat3860 (talk) 07:02, 11 November 2026 (UTC)
- We can do a watchlist notice but I also wanted that banner that shows at the top of pages when things are happening. I don't know what it's called. Theeverywhereperson talk here In solidarity! 07:01, 11 November 2026 (UTC)
- I've never done that before and I'm not familiar with the process. Do you mean a watchlist notice? Rusalkii (talk) 04:43, 11 November 2026 (UTC)
- Packrat3860 Maltazarian It would be nice if we had it December-2026 to January 2027, I just pinged you to get your opinions. Signup opens 25 November, and Rusalkii is it possible for you to design a banner/ that thing that shows up at the top, then publish it when signups start? Theeverywhereperson talk here In solidarity! 04:34, 11 November 2026 (UTC)
- Added, thanks. Packrat3860 (talk) 19:55, 9 November 2026 (UTC)
- I asked about how to run a different backlog drive over here on the Village Pump a few months ago, and the answers I got might be interesting or helpful. Dreamyshade (talk) 03:43, 12 November 2026 (UTC)
Template:Too many photos listed at Requested moves
[edit]
A requested move discussion has been initiated for Template:Too many photos to be moved to Template:Too many images. This page is of interest to this WikiProject and interested members may want to participate in the discussion here. —RMCD bot 22:49, 10 November 2026 (UTC)
- To opt out of RM notifications on this page, transclude {{bots|deny=RMCD bot}}, or set up Article alerts for this WikiProject.
Lead time estimate
[edit]Backlog is big and we get a lot of folks poking in various forums because they're worried their ticket has been missed. The {{edit COI}} already says to be "extremely patient" but it's not clear how long that actually means to wait. I was thinking we could maybe get like a median wait time? I don't know how hard it is to get that data and whether it's appropriate to put in the warning the template has for open tickets, but it might cut down on people venturing into the Teahouse or help desk asking why nobody has looked at their request yet. Packrat3860 (talk) 18:12, 12 November 2026 (UTC)
- https://editrequests.wiki/ has a median of 28 days, haven't checked their data. Rusalkii (talk) 01:34, 13 November 2026 (UTC)
Some thoughts on the COI queue
[edit]I've been trying to do a few of these when I have time over the last week, and have read through a lot more. Some observations:
- The volume is increasing much faster than our curren capacity to deal with it - in the six weeks since 1st October, there's been an average of about 40 new requests per day, and in the last two weeks, closer to 50. In that time we've been closing twenty a day. In the same time period last year we had an average of ten new requests per day (and nine closed).
- A very high proportion are AI-generated (or at least significantly AI-assisted). This tends to mean that they are very wordy and it can take some time to work out what the problem is.
- It's common to suggest a new/rewritten paragraph (or even the entire article). Sometimes this is obviously AI-generated, and sometimes it's not quite so obvious but the rest of the request is clearly AI, so it's a safe bet the new paragraph is.
- A lot of the requests are paradoxically much more minor than I expected - BLPs with "can you add this extra thing to my list of works", corporate ones along the lines of "please update our 2026 financials". It often feels more like an editorial pass than a request for a substantive correction. It is rare to see a COI request on a high-profile article (though it could be that those are spotted and resolved quickly by normal editing)
- Some of the requesters have a surprisingly minor level of COI ("I work in this field, please add X mundane detail sourced to neutral third parties"), but have got channeled to this request mechanism. This is quite refreshing to see, and it's great to err on the side of caution, but it does drive the volume up.
I don't think anyone would disagree that AI is likely to be the ultimate driver here (at least for #1-4). Quite why it has taken off so much in the last few months is debatable - I've seen a suggestion that this might be linked to newer AI tools finding things to do - "oh, there's a Wikipedia article about you, can we make it better?" rather than it just being a matter of AI lowering the barrier to entry for writing requests (in which case we would have expected to see it sooner than 2026). But it's undeniably here.
It makes it very easy to generate long and complex edit requests picking up on multiple issues, including very minor ones. These are in turn hard for volunteers, because a) they take a lot of time to read through and understand, and b) they're often relatively minor so they're not very engaging. It can also lead to heavy use of AI when requestors reply to queries about the edit requests, which can be difficult to deal with.
It also means that a lot of the suggested edits in #3 are either obviously AI-generated, or seem contextually likely to be even without clear markers, which means editors can't just copy and paste them without worrying about "laundering" AI-generated material. It is quite common to just have a substantial proposed change with no particular explanation, so the volunteer has to then work out what the changes are before deciding whether they need accepted and rewritten.
And, finally, the volume of minor COI requests increases the risk of missing the significant ones.
The recent AN dicussion at Wikipedia:Administrators' noticeboard/Archive384#Nearly 1000 outstanding COI edit requests was inconclusive but I think showed a sense that edit requests are a tolerated exception to the general approach of WP:LLMTALK. Even as someone who takes a fairly absolutist position on LLMTALK, I think this is reasonable - these are people not generally familiar with our processes and it helps us all if the problems can be clearly stated, plus we don't want to reject valid requests purely on grounds of form.
Some possible thoughts on ways to help handle the volume: not wedded to any of these, but just some suggestions.
- Looking at the Wikipedia:Edit Request Wizard, we could ...
- restructure it to take a "say what the problem is" approach rather than "suggest a proposed rewrite", if the majority of suggested rewrites are AI-generated and so cannot be used directly
- investigate whether there is anything we can put in the request wizard that would prompt the LLM as to the sort of request we want to see ("clear but concise, identify issues but don't provide a rewrite, etc")
- include some form of self-triage, eg "cosmetic fix", "routine update", "high priority", specifying that the latter is for things like vandalism, though it is possible we'd just end up with everything getting tagged that way. I note there is already a "small requests" / "large requests" workflow, with the latter adding the
|R, but I'm not sure if it does anything beyond that.
- From the AI-usage side, we could ...
- formalise how we permit AI to be used in edit requests, one way or the other - though there are good arguments for leaving it in a grey area. An explicit prohibition is likely to be ignored and it's difficult to see that closing a serious edit request just for using AI would be desirable.
- make it explicit to reviewers that they are permitted to decline any "please add this new section" or "please replace X paragraph with Y" where the proposed text is likely AI-generated in its own right, or presumed to be such (eg part of an AI-generated edit request), on the basis of our usual mainspace LLM prohibitions. Having the LLM-detector tagging systems work in talkspace as well as mainspace would be useful here in identifying such cases (and I believe this has been requested)
Ultimately I think we're going to struggle to cope with this in future unless we can change the sort of thing that is coming in - a backlog drive will make a dent but the numbers will climb steeply as soon as it's over. Andrew Gray (talk) 22:50, 13 November 2026 (UTC)
- "Say what the problem" type requests will simply not be actioned unless the problem is very blatant and the fix is straightforward, that's just asking volunteers to do all the work. I would not action such requests unless they were pointing out clear BLP violations or similar cases which are actively harmful instead of merely could-be-better. The rest of your ideas seem worth investigating - somewhere on my todolist is revamping the wizard, but I have no idea when I'll actually get to it. Rusalkii (talk) 23:01, 13 November 2026 (UTC)
- Articles for Creation recently added an AI disclosure step in its wizard at Wikipedia:Articles for creation/Submitting, including asking people to share a link to their chat transcript. Looking at the transcripts has been helpful for developing a better understanding of how people are using chatbots for drafting articles and what the chatbots are telling them about Wikipedia guidelines (samples, discussion). Could be a helpful step to add to this wizard while figuring out what else to do. Dreamyshade (talk) 07:55, 14 November 2026 (UTC)
- There's some further analysis of chat transcripts at User:Athanelar/Chatbot transcript analyses by the way. Athanelar (talk) 09:26, 15 November 2026 (UTC)
- "formalise how we permit AI to be used in edit requests" isn't something that shouldn't be done because it's a grey area, but because it's not really possible. New editors/requesters simply can't know about our formal permits, and we have no control over LLMs anyway so any permitting doesn't do much on its own. If we want to influence how AI is used in edit requests, the best way is probably through the Edit Request Wizard. Sadly, this probably means crafting some quite blunt instructions for the LLM to ingest.Doesn't the current wizard already promote a "say what the problem is" approach? It by default gives me "What I think should be changed" and "Why it should be changed" as the questions to fill. We should probably include the instructions "Neutrally worded, Concise, Supported by reliable sources, Not controversial, Has a descriptive subject line, such as "Conflict of Interest edit request" as a hidden note in the edit request as well as just being on the wizard, for anyone who copies everything into an LLM and asks the LLM to answer the questions. CMD (talk) 09:50, 14 November 2026 (UTC)
- That's a good idea, and the one thing that's paramount is adding little notes to tell them (as well as the chatbots as they'll pick it up, since it seems like there are the main source of the request pool becoming larger). We'll also need to encourage people to be clear, concise and precise, as this allows it to be easier to sort out the requests. Finally, the people whose COIs are very multi-layered (as in, I know a guy who's friends with the 3rd cousin/works in an area relating to this company/of this person) should be encouraged to edit by themselves, and these would be passed at roughly the same time as the backlog drive being planned, or even before. Theeverywhereperson talk here In solidarity! 10:48, 14 November 2026 (UTC)
- I think the number of people in the COI queue whose cousin's roommate's dog's vet is the article subject are pretty rare, and by encouraging them to edit we also end up nudging a number of people who genuinely have a COI to edit as well. As long as people clarify what the nature of the COI is, for those people we can just tell them to do it themselves after the request and that takes 30 seconds. We want to mostly decrease the number of requests which are difficult to review. Trying to prompt the LLMs in the wizard to be more useful and concise is a very good idea, as is sharing the chat transcript. Rusalkii (talk) 17:27, 14 November 2026 (UTC)
- Agree that replying and saying "that looks fine, we appreciate you checking but we're happy for you to go ahead and do it" (maybe with a gentle NOLLM reminder) sounds sensible in these cases. I wonder if we would need to adjust any of the COI guidance to acknowledge that's a good and acceptable outcome? Andrew Gray (talk) 21:16, 14 November 2026 (UTC)
- One of the response options is
{{edit COI|G}}which is "Go Ahead". Packrat3860 (talk) 21:55, 14 November 2026 (UTC)- That sounds great - I think I'd missed that. It should help clear out a good few of them, though I guess it'll work best on recent requests and not backlog ones. Andrew Gray (talk) 09:52, 15 November 2026 (UTC)
- One of the response options is
- Agree that replying and saying "that looks fine, we appreciate you checking but we're happy for you to go ahead and do it" (maybe with a gentle NOLLM reminder) sounds sensible in these cases. I wonder if we would need to adjust any of the COI guidance to acknowledge that's a good and acceptable outcome? Andrew Gray (talk) 21:16, 14 November 2026 (UTC)
- I think the number of people in the COI queue whose cousin's roommate's dog's vet is the article subject are pretty rare, and by encouraging them to edit we also end up nudging a number of people who genuinely have a COI to edit as well. As long as people clarify what the nature of the COI is, for those people we can just tell them to do it themselves after the request and that takes 30 seconds. We want to mostly decrease the number of requests which are difficult to review. Trying to prompt the LLMs in the wizard to be more useful and concise is a very good idea, as is sharing the chat transcript. Rusalkii (talk) 17:27, 14 November 2026 (UTC)
- That's a good idea, and the one thing that's paramount is adding little notes to tell them (as well as the chatbots as they'll pick it up, since it seems like there are the main source of the request pool becoming larger). We'll also need to encourage people to be clear, concise and precise, as this allows it to be easier to sort out the requests. Finally, the people whose COIs are very multi-layered (as in, I know a guy who's friends with the 3rd cousin/works in an area relating to this company/of this person) should be encouraged to edit by themselves, and these would be passed at roughly the same time as the backlog drive being planned, or even before. Theeverywhereperson talk here In solidarity! 10:48, 14 November 2026 (UTC)
- I think there are certainly ways the request process could be improved. I've been meaning to find an appropriate venue to ask/suggest whether Wikipedia has some kind of publicly visible agent instructions. The big LLM vendors (OpenAI, Anthropic, etc.) have invested quite a bit in the design of systems to give hints to agents so something telling them what they should and should not be doing might cut down on pointless cruft. I expect such a suggestion would be contentious given that having official AI instructions is in tension with WP:NOLLM, and it wouldn't stop somebody who is dedicated enough to specifically override those instructions (or use an open model designed not to listen to them), but I think it could do a lot of good.
- Additionally I wanted to point out with regards to the proposed drive, the goal isn't necessarily just to bring down the backlog. It's true that if the additional help disappears as soon as the drive is over that we'll be right back where we started (more requests coming in than reviewers are closing means the backlog inevitable grows). However part of the goal of the drive is to entice editors who have not otherwise done this work to consider it. If we can get a handful of people to become "permanent" COI reviewers even at a relatively modest volume, it'll make a big difference. Packrat3860 (talk) 20:12, 14 November 2026 (UTC)
- @Packrat3860 You may be interested in the Wikipedia:Village pump (policy)#Wikipedia:AI agent policy discussion. CMD (talk) 23:02, 14 November 2026 (UTC)
- Also as far as structuring the request wizard to highlight the bits that are most important, the #1 thing I'm always looking for is "what is the source that supports the change". If they want some big block of text inserted it's helpful to have the text (ideally formatted with inline citations) but the source is the thing that makes or breaks most requests in my experience, and evaluating them is most of the work. I have also been thinking it might be nice to encourage more of these COI editors to use
{{Refideas}}when what they want is just to have somebody maybe update the article as a result of new info. Packrat3860 (talk) 20:18, 14 November 2026 (UTC) - I think the obvious answer to tackling this backlog is to not equivocate about AI usage. If we miss a couple of productive edits because we presumptively deny LLM requests, so be it. If the whole request is AI generated, any content they propose is also overwhelmingly likely to have been AI generated. Sometimes it might just be a line change which is uncontroversial, and that would be a shame to deny, but if it's any more substantive prose then accepting it would be a NOLLM violation anyway.
- Whenever I dive into the COI ER queue, I would say that somewhere in the region of 70-80% of the requests I see are AI generated, and I presumptively decline these. I then usually check the article they're attached to, and very often they're deletion material anyway, but that's another issue. Athanelar (talk) 09:46, 15 November 2026 (UTC)
Requesting too many edits under COI
[edit]Hello. I am a new editor who has declared conflict of interest. I am being paid to edit a university's page -- I used to work there, but have retired. Because I am familiar with the organization and I have a background in journalism, they have asked me to update and rewrite their wiki page. I have declared this conflict on my userpage and I am mainly updating or adding more information to the TRU page from a neutral, factual perspective.
To be honest, the university's page is kind of messy and not well written in lots of areas. If I could, I would delete the whole thing and start from scratch, but I understand that's not doable or advisable. Instead, I have submitted for review a fairly large edit of one section, and have just finished editing a second section that I would like to submit for review as well.
However, I see that there is a backlog and I want to be respectful of other editors' time.
What I'd like to know is, can I submit more than one edit for review at a time? If I am only allowed one edit review request at a time, is there a way I can submit the second section edit in place of the first request? The second one is a higher priority because it contains outdated information about a controversy at the university and it includes an inference that the president resigned due to this controversy when, in fact, he actually just gave two years' notice to retire. It would be nice to clear it all up so it is accurate — not favouring one side or the other.
I am still learning the ropes, but I want to be respectful and follow the rules.
Your help is much appreciated. Pandamundo (talk) 20:07, 14 November 2026 (UTC)
- @Pandamundo you can submit more than one at a time. Editors will usually prioritize requests which are correcting factual errors over other requests. Another way to make it more likely to be answered is to split out just the factual correction, without any extra edits that may be difficult to review. Rusalkii (talk) 20:14, 14 November 2026 (UTC)
- Thank you @Rusalkii! The second request is just for the two or three paragraphs involving the controversy. Is there a way I can label it so editors can see it is a factual correction? Pandamundo (talk) 20:16, 14 November 2026 (UTC)
- Just mention it in the text of the request, we don't have a good way to label them in any formal manner. Rusalkii (talk) 06:30, 15 November 2026 (UTC)
- Thank you @Rusalkii! The second request is just for the two or three paragraphs involving the controversy. Is there a way I can label it so editors can see it is a factual correction? Pandamundo (talk) 20:16, 14 November 2026 (UTC)