Wikipedia talk:WikiProject Articles for creation

From WikiProjectMed
Jump to navigation Jump to search
    Main pageTalk pageSubmissions
    Category — List (sorting)    		ShowcaseParticipants
    Apply — By subject    		Reviewing instructions
    		Help deskBacklog
    drives
    Welcome—discuss matters concerning this project!
    AfC submissions
    Random submission
    3+ months
    2,812 pending submissions
    Purge to update
    Shortcut


    Skip to top
    Skip to bottom
    WikiProject iconArticles for creation Project‑class
    WikiProject iconThis page is used for the administration of the Articles for Creation or Files for Upload processes and is therefore within the scope of WikiProject Articles for Creation. Please direct any queries to the discussion page.Articles for creationWikipedia:WikiProject Articles for creationTemplate:WikiProject Articles for creation (admin)AfC project pagesWikiProject icon
    ProjectThis page does not require a rating on Wikipedia's content assessment scale.

    AFC helper script update

    I deployed a small update to the AFC helper script tonight. The two main things in this deploy are 1) there is now a check box to copy over comments to the talk page, and 2) better autofill of a person's name in the DEFAULTSORT box on the accept screen. I have a bunch more in the pipeline. Will keep you posted. –Novem Linguae (talk) 07:41, 11 April 2024 (UTC)[reply]

    I have been following via the storm of git emails recently. Good work at getting some progress on these outstanding issues. Cheers KylieTastic (talk) 09:13, 11 April 2024 (UTC)[reply]
    Tracked in github.com
    Issue #333
    Resolved
    There's an issue where AFCH is adding the section header without a line break. I've opened a ticket. —TechnoSquirrel69 (sigh) 00:07, 12 April 2024 (UTC)[reply]
    Sorry, that come off as a bit curt, didn't it? Thanks to the AFCH maintainers who implemented the copying of comments to the talk page; I think a lot of reviewers, including me, will be pleased to hear it! —TechnoSquirrel69 (sigh) 00:11, 12 April 2024 (UTC)[reply]
    Your message was fine. Thanks for quickly reporting on GitHub. I think I got the fix out in 13 minutes from when I got the GitHub email :) –Novem Linguae (talk) 00:39, 12 April 2024 (UTC)[reply]

    Upcoming features

    Howdy folks. I'm excited to announce I've written AFC helper script patches for several frequently requested tickets. You can visit the patches and check out the screenshots to make sure you like them. If you're a techie (cc SD0001), you can click on the "Files changed" tab to see the code I wrote and review it. I plan to merge and deploy these patches on Monday.

    So far I've cleared out the queue of other people's patches, cleared out the queue of tickets marked easy, and am about halfway through clearing out the high priority (frequently requested) queue. Will probably work on AFCH for another week to finish clearing out the high priority queue, then switch to a new project. There is no shortage of programming stuff to work on in the movement.

    Anyway, I hope y'all like these patches. If you want me to adjust anything, let me know before Monday. Thank you. –Novem Linguae (talk) 00:47, 19 April 2024 (UTC)[reply]

    Thanks so much for doing these, NL. I know a lot of reviewers have been wanting these features for years. — Ingenuity (talk • contribs) 00:56, 19 April 2024 (UTC)[reply]
    Seconding Ingenuity — thank you so much! —TechnoSquirrel69 (sigh) 01:23, 19 April 2024 (UTC)[reply]
    Good work, sorry but real-life issues mean I probably won't get time to review the code. KylieTastic (talk) 07:28, 19 April 2024 (UTC)[reply]
    Been a delight to see this getting processed. Primefac (talk) 11:59, 19 April 2024 (UTC)[reply]
    Thanks all. The new features are live. Please keep an eye out for bugs. P.S. An additional feature not mentioned above is the TurnItIn copyright detection warning will now show (it was broken before). –Novem Linguae (talk) 08:19, 23 April 2024 (UTC)[reply]
    @Novem Linguae: Hate to be the bearer of bad news after such a while, but I haven't been reviewing at AfC very much recently. The auto-subscribe feature did not take effect on this decline. I have Convenient Discussions enabled, which may have something to do with it, but I don't know enough about it or AFCH to be sure about that. —TechnoSquirrel69 (sigh) 01:30, 12 May 2024 (UTC)[reply]

    Newsletter?

    Cheers Novem Linguae. As the subscribe feature is a new preference we really could do with a way to tell people that it is now an option especially as we know from past discussions that a lot don't even notice the preferences. I'm not sure how many reviewers even watch this page. KylieTastic (talk) 09:17, 23 April 2024 (UTC)[reply]
    Cool stuff @Novem Linguae! @KylieTastic and others, what you think about a newsletter? S0091 (talk) 16:22, 23 April 2024 (UTC)[reply]
    @S0091 by newsletter I assume you mean a mass message? Why not, we've never sent many. A short post highlighting the tool improvements and maybe a general poke about the backlog growing and any other news? KylieTastic (talk) 17:24, 23 April 2024 (UTC)[reply]
    Yes, mass message. I don't mind trying to do one but will need some help. Is there an example of one from the past somewhere? S0091 (talk) 17:35, 23 April 2024 (UTC)[reply]
    Wikipedia:New pages patrol/Newsletter#Newsletter archive may provide some ideas, templates, etc. –Novem Linguae (talk) 00:50, 24 April 2024 (UTC)[reply]

    Double signature bug

    Tracked in github.com
    Issue #347
    • Possible minor issue Novem Linguae... I just noticed on a couple of declines an extra signature on the user talk page messages (this and this) however the first I did after your announcement this morning this does not have the issue, so it appeared after changing my preferences (I enabled 'Do not add pages to watchlist' and 'Receive a notification....'). I played in my sandbox with different settings but it didn't happen so maybe it's only on new pages or something? Cheers KylieTastic (talk) 20:58, 23 April 2024 (UTC)[reply]
      That's probably the discussiontools API (which I use for subscriptions) auto adding a signature. Definitely a bug. Will work on fixing. –Novem Linguae (talk) 00:51, 24 April 2024 (UTC)[reply]
      OK, this bug happens when 1) the user talk page doesn't exist yet and 2) the user's preferences are set to auto subscribe. The simplest fix is to stop auto adding {{Talk header}}s to the user talk pages that AFC helper script creates. I've written a patch for that if anyone wants to comment. Will probably deploy it tomorrow unless there's objections. –Novem Linguae (talk) 02:33, 25 April 2024 (UTC)[reply]
      This one should be fixed on Thursday when MediaWiki core auto deploys. Someone wrote a patch for this upstream :) –Novem Linguae (talk) 09:45, 4 May 2024 (UTC)[reply]
      And the update has finally hit and yes it's fixed the issue KylieTastic (talk) 21:09, 9 May 2024 (UTC)[reply]
      Yay. We can cross another bug off the list :) –Novem Linguae (talk) 23:39, 9 May 2024 (UTC)[reply]

    Commenting causes 'edit conflict'

    Tracked in github.com
    Issue #352
    Resolved

    For the last few days, when I try to add a comment using AFCH, I get an 'edit conflict' error message for no obvious reason. I think this has (so far at least) only happened when I try to do that straight after I've just done a decline/reject, but I'm not sure; will keep an eye on it. Reloading the page and relaunching AFCH resolves the issue, so it's no biggie, just a bit annoying. -- DoubleGrazing (talk) 06:22, 25 April 2024 (UTC)[reply]

    That's probably the edit conflict detection feature that we released a few days ago. As you say, it's probably detecting your decline as an edit conflict. Don't forget that there's a comment box on the decline/reject screens, so you can just type your comment there before clicking decline/reject. Then, if I'm understanding you right, you wouldn't need to reload the page. –Novem Linguae (talk) 06:47, 25 April 2024 (UTC)[reply]
    That's what I figured. Is there a time limit (from the decline/reject) within which a comment gets treated as an EC? In other words, would it help if I waited, say, 5+ sec before commenting?
    As an aside, rightly or wrongly, when declining, I don't like to put into the comment box anything which isn't related to the decline, I rather add it as a separate comment. So if I decline eg. for notability, and there is also a problem with formatting or layout etc. which I feel compelled (!) to remark upon, I do that after my decline so it's clear that isn't why I declined. -- DoubleGrazing (talk) 07:04, 25 April 2024 (UTC)[reply]
    The algorithm doesn't look at time. It triggers if there's an edit after the page is loaded. Perhaps I could look into making it only detect edits from other people, and not edits from yourself. Stay tuned. –Novem Linguae (talk) 07:14, 25 April 2024 (UTC)[reply]
    A patch to only detect other people's edits as an edit conflict ended up being pretty easy. Will deploy it in the next day or two. –Novem Linguae (talk) 08:02, 25 April 2024 (UTC)[reply]
    Thanks @Novem Linguae, appreciate it! :) DoubleGrazing (talk) 08:06, 25 April 2024 (UTC)[reply]
    Deployed. Will take effect within 15 minute as caches clear. –Novem Linguae (talk) 01:31, 26 April 2024 (UTC)[reply]
    Not sure if anyone else is still having the issue but I am. Even without placing a comment I get the warning when I decline a draft. --CNMall41 (talk) 02:26, 26 April 2024 (UTC)[reply]
    Was able to reproduce. I've reverted the changes for now (will take up to 15 minutes to take effect) and will fix when I get back from dinner. Thanks for reporting. –Novem Linguae (talk) 02:46, 26 April 2024 (UTC)[reply]
    Perfect. I just performed it on a new AfC submission as well as the one I was attempting when I first received the error message. Both work fine. Thanks for fixing!!!!!! --CNMall41 (talk) 03:43, 26 April 2024 (UTC)[reply]
    I wrote and deployed a patch for this today. Hopefully this one is resolved now. Let me know if it goes awry again. –Novem Linguae (talk) 09:46, 4 May 2024 (UTC)[reply]
    Thanks for persisting, @Novem Linguae, but it's still happening. Do I need to do something at my end, like clear my caches, or should it be working automatically? -- DoubleGrazing (talk) 09:45, 5 May 2024 (UTC)[reply]
    Should just work. Ill take a look and report back. –Novem Linguae (talk) 01:14, 6 May 2024 (UTC)[reply]
    I hadn't read this page for a few weeks and just noticed this, which I think I did observe also a few weeks ago. But I have also encountered a different edit conflict situation that I have reported below, which really is a case of detecting and preventing a race condition. Robert McClenon (talk) 21:42, 15 May 2024 (UTC)[reply]

    Television Season Articles

    Myself and other editors at WikiProject Television have noticed that a few AFC reviewers have been accepting a few subpar submissions that don't meet the requirements of Wikipedia:Notability (television) and Manual of Style/Television#Article Splitting. You can see the relevant discussions here and here. These are essentially creating an unnecessary SPINOUT and duplication of information that already exists elsewhere. Additionally, it takes time on our part to clean these up when they could've just been rejected to begin with. General consensus is that season articles require extensive information in areas of production, casting, reception, and other areas, to establish that the season is notable outside of the series as a whole. Similar to other topics on Wikipedia, notability for seasons are not automatically inherited from that of the parent article. TheDoctorWho (talk) 16:46, 30 April 2024 (UTC)[reply]

    @TheDoctorWho: the user Rickt11, who moved the two The Rookie articles to main space, is not an AfC reviewer, I believe? -- DoubleGrazing (talk) 17:06, 30 April 2024 (UTC)[reply]
    I was just writing the same - Rickt11 is not an AfC reviewer they just removed the AfC tags then moved the articles. It appears that no one pinged them in the project discussion or left a message on their talk page. If you have a problem with someones actions it is not usually a good step to talk to them? KylieTastic (talk) 17:07, 30 April 2024 (UTC)[reply]
    On the other hand, the three CSI drafts were approved by three different reviewers (1, 2, 3), so there is still an argument to be made here. Primefac (talk) 17:09, 30 April 2024 (UTC)[reply]
    I agree, it's good to bring it up here as well when its more than one reviewer involved, just also good to let involved people know as well KylieTastic (talk) 17:12, 30 April 2024 (UTC)[reply]
    For the second one Draft:CSI: Vegas season 1 was accepted by CNMall41 and Draft:CSI: Vegas season 2 was accepted by Ozzie10aaaa (both actual reviewers) - courtesy pinging both. KylieTastic (talk) 17:10, 30 April 2024 (UTC)[reply]
    Thanks for the ping. I don't recall this too in-depth but looks like the individual seasons do get the coverage needed to establish notability. Yes, they are covered on the main CSI Vegas page, but once the individual seasons gain notability they can be split into separate pages and the majority of that information should be removed from the main page. As far as the move, I never have any issue with someone objecting to an approval I made. However, I would always recommend to go AfD as opposed to sending something an AfC reviewer approved back to draft. Otherwise it defeats the purpose of AfC. --CNMall41 (talk) 19:16, 30 April 2024 (UTC)[reply]
    agree w/ CNMall41--Ozzie10aaaa (talk) 12:08, 2 May 2024 (UTC)[reply]
    I'm with you in spirit, and would reinforce it with there being a wp:not argument against some of those. I also like what's in those two things that you linked. But as a structural note, Wikipedia:Notability (television) is an essay, and Manual of Style/Television#Article Splitting is guidance on a splitting action, not a rule for existence of an article. Again, I like what's in both of them but IMO AFC folks should not be criticized for not treating these as requirements for existence of an article / declining articles on those grounds. North8000 (talk) 12:31, 2 May 2024 (UTC)[reply]

    Note that Draft:CSI: Vegas season 1, Draft:CSI: Vegas season 2 and Draft:CSI: Vegas season 3 have been updated and resubmitted if you want to take a look. KylieTastic (talk) 14:04, 10 May 2024 (UTC)[reply]

    Multiple Sales-essay drafts from new users.

    Four articles, all today, all from new users, all sales-related essays. What's going on?

    Qcne (talk) 17:29, 4 May 2024 (UTC)[reply]

    Deletion review for Category:G13 eligible AfC submissions

    An editor has asked for a deletion review of Category:G13 eligible AfC submissions. Because you closed the deletion discussion for this page, speedily deleted it, or otherwise were interested in the page, you might want to participate in the deletion review. –LaundryPizza03 (dc̄) 22:35, 4 May 2024 (UTC)[reply]

    Signature wikicode problem?

    Tracked in github.com
    Issue #358

    I'm not sure if this has come up before but I've noticed that whenever I try to provide a decline reason, my comments doesn't seem to show up. Maybe there's something off with my signature wikicode? @Novem Linguae: —Saqib (talk | contribs) 10:09, 8 May 2024 (UTC)[reply]

    @Saqib an example of a decline this happened on would be helpful. Cheers KylieTastic (talk) 10:14, 8 May 2024 (UTC)[reply]
    See this, this and this. —Saqib (talk | contribs) 10:21, 8 May 2024 (UTC)[reply]
    The vertical bar in your signature is confusing the template that your comment is being inserted into. Vertical bar is a special character in templates. I'll open a ticket for AFCH. But if you don't want to wait for a patch, you can always modify your signature and remove/replace the vertical bar with something else. Hope that helps. –Novem Linguae (talk) 10:37, 8 May 2024 (UTC)[reply]
    No reason to patch as that will break lots of other things as well. See the instructions under the signature config Note: to use a displayed pipe ("|") character (i.e. not part of a piped link), please use | for the pipe character; otherwise, it may cause templates to fail. KylieTastic (talk) 10:39, 8 May 2024 (UTC)[reply]
    I think an algorithm could be written to fix this without breaking other things. The algorithm would be to check the comment for special template characters such as = and |, discard any it finds that are inside of additional templates, and replace them with escaped equivalents such as {{=}} and {{!}}. –Novem Linguae (talk) 10:42, 8 May 2024 (UTC)[reply]
    Thanks.  Fixed —Saqib (talk I contribs) 10:44, 8 May 2024 (UTC)[reply]
    Yes it can be patched but that just masks the issue and someone with a signature like that may not notice it breaking other places. Really the place this should be patch is in the user preferences... it should detect issues and stop you using it :/ KylieTastic (talk) 10:45, 8 May 2024 (UTC)[reply]

    Remember Taiwan 1000?

    Back in the end of 2023, we had a spike of submissions from Taiwanese, which resulted in a number of discussions here, 1, 2, 3, 4. The project administrators are presenting their experience organising the activity in 2.5 hours time at meta:ESEAP Conference 2024 for a lightning session (15 minutes)! The session will be livestreamed (and likely subsequently uploaded to commons). Do tune in at YouTube at May 11, 2024, 8:00 UTC. (conference timetable).

    Sorry for the short notice, I have been up at my neck with various commitments. Pinging the following reviewers who had participated in the previous conversations here for awareness: @GoingBatty, @Novem Linguae, @S0091, @Asilvering, @North8000. I will present for the lightning talk as part of the audience, but may end up participate in the QnA or sharing my experience as one of the AfC reviewers having dealt with this project as well (who knows?). – robertsky (talk) 05:34, 11 May 2024 (UTC)[reply]

    I missed this, but I'd be interested to read a summary of the talk if you're so inclined. -- asilvering (talk) 20:50, 11 May 2024 (UTC)[reply]
    I am waiting for the recording to be made available. Will update when ready. – robertsky (talk) 18:22, 15 May 2024 (UTC)[reply]

    Category:G13 eligible AfC submissions has been nominated for discussion

    Category:G13 eligible AfC submissions has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether it complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. Primefac (talk) 18:13, 12 May 2024 (UTC)[reply]

    Input from the project would be good, I will not give my opinion here but needless to say I think our project should have an input on the categories we use to manage it. Primefac (talk) 11:27, 15 May 2024 (UTC)[reply]

    Removal of Captbloodrock

    Since User:Captbloodrock has been blocked for sockpuppetry, they should probably be removed from the list of probationary members. jlwoodwa (talk) 04:09, 15 May 2024 (UTC)[reply]

    The tool shows this user completed 0 reviews, for the record. —TechnoSquirrel69 (sigh) 05:19, 15 May 2024 (UTC)[reply]
    Done; thanks. Extraordinary Writ (talk) 08:15, 15 May 2024 (UTC)[reply]
    Thanks Extraordinary Writ. Primefac (talk) 11:22, 15 May 2024 (UTC)[reply]
    I was going to get to it this weekend as usual but per the above someone beat me to it.
    Genuinely curious, though... why does it matter if a blocked user is on the list? This is the third or fourth time in recent history that someone posts here (or contacts me directly) about a user needing removed. I don't really mind; it seems a bit unnecessary but I'm happy to adjust my editing habits if folks want it. Primefac (talk) 11:22, 15 May 2024 (UTC)[reply]
    I like the idea of removing sockpuppets in an effort to deny recognition; we simply move on without acknowledging their disruption. Also, in these cases it's quite obvious the user account will never be reviewing at AfC again, so there's little point in listing them among other active WikiProject members. —TechnoSquirrel69 (sigh) 15:29, 15 May 2024 (UTC)[reply]
    I think it's useful to see the true number of reviewers, so we have a good idea of who is active or not. Qcne (talk) 15:35, 15 May 2024 (UTC)[reply]
    Oh, I get that; I had seen they were blocked and was going to remove them next time I was going in that direction. I guess the urgency is what I'm asking about. Then again, it just could be me reacting to someone asking to do something I'm already planning on doing (not quite ODD but in that same vein). Primefac (talk) 17:55, 15 May 2024 (UTC)[reply]

    Draft:Michiko Iseri

    Comments are invited on my draftification of this article which I believe was prematurely and erroneously moved to main space by a non-reviewer (no harm in their status, it is simply a statement of fact).

    If consensus says I am in error please return the draft to mainspace. 🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦 17:52, 15 May 2024 (UTC)[reply]

    Another Type of Edit Conflict

    There is a description above, from a few weeks ago, of a situation where the AFCH script detects an edit conflict with itself. I consider that situation to be neither a bug nor a feature, but something in between, a harmless oddity. I have, at least twice recently, encountered a slightly different edit conflict, also the result of the edit conflict detection feature, which is surprising, but is a case of two things working correctly, and so is a feature. If I view the list of submitted pages in user space, I may see a few user sandboxes that have been submitted for review. What I do is to see if there is an obvious title, which there will be if the sandbox has a proper lede sentence. If so, I move the sandbox page to draft space, with the appropriate title. Then I give the draft a quick review for any obvious fails, such as no references. If so, I decline, or occasionally reject, the draft, with the appropriate code, and one or more templates, such as {{seefoot}}. Sometimes the script gives me an error message saying that there was an edit conflict. A look at the history may show that a bot, usually RichBot, has edited the draft. RichBot has removed a template that is not used in draft space. This is unexpected, unless one is expecting it, but is entirely correct, because the bot is checking new draft pages, including new draft pages created by moving, and the bot is fast, because it is a bot. The edit conflict detector is also completely correct, because otherwise the script would be overwriting the edit by the bot, and therefore re-inserting the {{User sandbox}} template that is not valid in draft space.

    So, if you see this behavior when reviewing a sandbox, it is entirely correct. Thank you, User:Novem Linguae, or whoever, and thank you, User:Rich Smith. Robert McClenon (talk) 21:37, 15 May 2024 (UTC)[reply]

    Thanks for the comments Robert McClenon, just to add, it doesn't *really* matter if AFCH does overwrite RichBot's edits, as it will just come and do them again next time :) - RichT|C|E-Mail 21:44, 15 May 2024 (UTC)[reply]
    Well, that's true. Bots can be persistent. Robert McClenon (talk) 17:40, 16 May 2024 (UTC)[reply]
    User:Rich Smith - What you are saying is that the design of the bot causes the race condition to be a non-critical race condition. Robert McClenon (talk) 20:22, 16 May 2024 (UTC)[reply]
    @Robert McClenon: In a fashion, I guess so. All I'm saying is, in that task, RichBot doesn't check if its edited the page before, and will do so again if the template re-appears - RichT|C|E-Mail 21:23, 16 May 2024 (UTC)[reply]

    Edit Conflicts with Yourself

    Just noting for the record (not that it's entirely on-topic) that if you first mark a draft as under review, and then try to carry out the review (accept/decline/reject), that also counts as two consecutive edits by you, triggering the edit conflict warning. -- DoubleGrazing (talk) 17:43, 16 May 2024 (UTC)[reply]
    Yes, User:DoubleGrazing. It appears that there are at least two situations in which the script detects an edit conflict. One is an edit conflict with oneself, as you describe, which is sort of a misfeature, because it is not actually a race condition, which is the computer science term for what Wikipedia edit conflicts are a variety of. The other is an edit conflict with a bot, which really is a race condition, because the bot has a different starting gun than is used for reviewers. The edit conflict detection for a bot is correct, while with marking a draft under review and then accepting the draft, there is no real race condition. Robert McClenon (talk) 20:13, 16 May 2024 (UTC)[reply]
    The case that I saw was where I saw that the draft should be accepted, but there was a blocking redirect. So I marked the draft under review and performed other reviews until I was ready to deal with the blocking redirect. I then checked whether the redirect had significant history, which would require a swap. On seeing that the redirect had minor history, I moved the redirect to limbo and tagged it as {{db-moved}}, and tried to accept the draft. I was able to accept the draft after I refreshed my view of the draft page. Is that similar to what User:DoubleGrazing is describing? Is that similar to what was described a few weeks ago? Robert McClenon (talk) 20:13, 16 May 2024 (UTC)[reply]

    Rating articles in the banner shell

    Tracked in github.com
    Issue #73

    Please could you modify your helper script to always put the WPAFC banner inside the banner shell (if one is already on the page) or to add a banner shell (if not). Also can you put the |class= parameter in the banner shell instead of individual project banners? This edit is not current best practice, and needs cleaning up by another editor later. Thanks! — Martin (MSGJ · talk) 08:35, 17 May 2024 (UTC)[reply]

    This issue has been raised almost every month this year (Jan, Feb, Mar). It is a known issue and is being tracked. Primefac (talk) 08:42, 17 May 2024 (UTC)[reply]
    I'll be traveling for a week. May have some time to work on this after that. I might need to do another burst of work on AFCH to fix some small bugs caused by the last patches, and fix these talk page wikicode bugs. –Novem Linguae (talk) 09:06, 17 May 2024 (UTC)[reply]
    Are you telling me this issue has been "tracked" since 2016 and is still not fixed? Would be great if Novem Linguae can spend some time on this and get it fixed. But ultimately people have to take responsibility for the edits they make using tools. If the tool cannot be fixed, then you may have to stop using the tool. — Martin (MSGJ · talk) 15:51, 20 May 2024 (UTC)[reply]
    Doesn't a bot go through and regularly fix WPBS issues in talkspace? This doesn't seem like a big enough problem to effectively shut down AfC over. jlwoodwa (talk) 18:16, 20 May 2024 (UTC)[reply]
    I think there is a bot but I can't think which at the mo. Until a helpful coder decides to fix the issue the simple thing is for reviewers to use a tool or manually fix up, personally I always run Rater after any accept. However we also have many Gnomes that will just fix up the issue. The case given is very rare, most have no banner shell, many have no talk page, so it really is not a huge issue and more of a nice to have. It should be remembered that AfC is primarily a notability check (as well as spam, attack, copy vio filter) and has no requirements to do clean up and accepts are they same as if these users could just create in main-space direct. I personally like to so as much tidy-up as I can but I have no desire to make it mandatory when we can't get enough reviewers as it is. KylieTastic (talk) 19:05, 20 May 2024 (UTC)[reply]
    Not placing any wikiproject tags is an option if this problem is severe. But would need consusus. –Novem Linguae (talk) 21:47, 20 May 2024 (UTC)[reply]

    Sockpuppet probationary reviewer TheChineseGroundnut

    Please see Wikipedia:Sockpuppet investigations/TheChineseGroundnut, where they are a likley UPE editor, editing in the same area as Wikipedia:Sockpuppet investigations/Tochi Clement 🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦 07:04, 20 May 2024 (UTC)[reply]

    I was wondering if I'd see their name pop up like this when I approved them... Primefac (talk) 07:09, 20 May 2024 (UTC)[reply]
    I've never been happy that Johnel was "accepted". The main editors have (now) been sock blocked. I am unsure whether there is any purpose in sending it to AfD, or whether an IAR draftification is appropriate. 🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦 07:45, 20 May 2024 (UTC)[reply]
    Huh. I thought there was something a bit off there, but wouldn't have imagined UPE related to Tochi Clement, esp. given that they started Wikipedia:Articles for deletion/Kourage Beatz. Or was that some sort of nefarious double bluff? -- DoubleGrazing (talk) 08:20, 20 May 2024 (UTC)[reply]
    Sometimes rivals try to interfere with each other. 🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦 11:22, 20 May 2024 (UTC)[reply]

    'BLP' decline

    Category:AfC submissions declined as BLP violations (14)

    The text of this submission has been removed from Wikipedia. Wikipedia has a strict policy concerning biographies of living persons; we cannot accept such articles if they are unsourced, or contain unverifiable information which is potentially defamatory. All articles about living persons must conform to our biographies of living persons policy. In order to permit the author of this submission to provide sources that may satisfy the policy, the text of the page is available in the history.

    I've just declined this Draft:Pune Porsche Crash case partly on the basis that there is unsupported potentially contentious information about living people. I used the BLP decline reason, and the resultant notice states that "The text of this submission has been removed from Wikipedia", but nothing has been removed, it's all still there. (Whether it actually needs to be removed is another matter, but if so then it can always be redacted as a separate exercise.) My question is, did I do something wrong, or is the tool not working correctly, or is it not even meant to remove anything? I can't remember if I've used this decline reason before, so don't know what was supposed to happen with it. -- DoubleGrazing (talk) 09:20, 22 May 2024 (UTC)[reply]

    Woah. I don't think I've ever used that before either. I wouldn't be opposed to just removing that first bolded sentence; if something needs removal that badly, it will likely need RD2 and a comment will do better to explain what and why it was removed (plus likely an additional warning on their user talk). Primefac (talk) 09:25, 22 May 2024 (UTC)[reply]
    I have used it a couple times and I manually blank the draft which is what I think "removed from Wikipedia' is intended to mean, similar to when you tag an page for G10 the text is automatically removed. S0091 (talk) 14:22, 22 May 2024 (UTC)[reply]
    Just noting (and I'll put the template above the quote) that there are currently only 14 drafts declined under this criteria, so it's not like it's being misused. Primefac (talk) 14:26, 22 May 2024 (UTC)[reply]
    @S0091: that's kind of what I was expecting would happen, that the content would be automatically deleted (indeed, like with G10, as you say), hence my wondering 'what gives?'
    BTW, the draft has been resubmitted, and while the referencing is better it's still not enough IMO to support all that speculation and innuendo. I'm also not sure that this is compliant with WP:NEWSEVENT, WP:BLP1E, WP:BLPCRIME, and/or possibly others. But I'll happily let someone else review it next. -- DoubleGrazing (talk) 14:39, 22 May 2024 (UTC)[reply]
    @DoubleGrazing I just rejected it under WP:NOTNEWS. I will not put up a struggle if another reviewer reverts this. 🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦 19:41, 22 May 2024 (UTC)[reply]

    Repeated comments

    Tracked in github.com
    Issue #206

    I reviewed and declined Draft:CaptionHub. It had already quite a lot of commentary from earlier reviewers, to which the draft author (presumably) had replied. When I declined it, all these comments somehow became repeated several times over. Anyone know why this happened? -- DoubleGrazing (talk) 06:35, 23 May 2024 (UTC)[reply]

    It seems this repetition happened both when I marked the draft as under review, and then again when I declined it [1]. -- DoubleGrazing (talk) 06:51, 23 May 2024 (UTC)[reply]
    It seems that if an {{AfC comment}} is malformed, AFCH for some reason duplicates it. See this previous discussion. It's being tracked, but I don't know if it's a super-high priority since it doesn't seem to happen often. Primefac (talk) 07:53, 23 May 2024 (UTC)[reply]
    Thanks @Primefac, didn't remember the earlier discussion on this. (I'm somewhat relieved to note that I wasn't at least part of it at the time!) -- DoubleGrazing (talk) 08:02, 23 May 2024 (UTC)[reply]
    Thanks for tidying it up, Ingenuity! I meant to but forgot. -- DoubleGrazing (talk) 11:17, 23 May 2024 (UTC)[reply]
    Will try to patch this in my next burst of AFCH work. Am travelling this week, so maybe in a week or two. –Novem Linguae (talk) 02:50, 24 May 2024 (UTC)[reply]
    Retrieved from "https://mdwiki.org/wiki/Wikipedia_talk:WikiProject_Articles_for_creation"