Misplaced Pages

talk:WikiProject Articles for creation: Difference between revisions - Misplaced Pages

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 17:34, 22 December 2024 editLowercase sigmabot III (talk | contribs)Bots, Template editors2,311,978 editsm Archiving 5 discussion(s) to Misplaced Pages talk:WikiProject Articles for creation/Archive 59) (bot← Previous edit Latest revision as of 10:52, 24 January 2025 edit undoSD0001 (talk | contribs)Interface administrators, Administrators16,181 edits Non-English drafts: additionTag: CD 
(160 intermediate revisions by 44 users not shown)
Line 24: Line 24:
--> -->


== Disable AFCH if there is an ongoing AfD ==
== Bots/scripts that detect that a submission has not changed (much) since the last time it was submitted ==


The AFCH tool should be disabled if there is an ongoing AfD at the corresponding mainspace title, as with ] and ], for example. ] (]) 16:47, 31 December 2024 (UTC)
Are there any bots/scripts that detect that a submission has not changed (much) since the last time it was submitted? Ideally they would be able to autoreject or at least put them on a list. It might be possible to look at the previous reason for rejection, e.g. not meeting GNG, and if no new refs are added it is highly unlikely it will pass this time. ] (]) 15:27, 10 November 2024 (UTC)
:No, and if I remember correctly we decided not to have any sort of bot that does this. ] (]) 15:35, 10 November 2024 (UTC) :Why? A draft like that should be declined as <code>exists</code> anyway, so disabling AFCH would mean that we wouldn't be able to do that. ] (]) 16:51, 31 December 2024 (UTC)
:I think having a bot that does this would be a bad idea. One poor decline could easily lead to a series of them. -- ] (]) 16:03, 10 November 2024 (UTC) ::In fairness, that (decline as 'exists') is what GTrang did with this draft, but it was reverted as {{tq|just extra administration for no reason}} (I think). Which then put the draft back in the pool. -- ] (]) 16:57, 31 December 2024 (UTC)
::For clarity, given @]'s comment below, my comment is about putting them on a list. (Obviously, I think an autoreject bot would be even worse.) -- ] (]) 19:42, 10 November 2024 (UTC) :::I have undone that edit as the AFD is clearly trending towards the article being kept. ] (]) 17:11, 31 December 2024 (UTC)
::::I went ahead and redirected the draft to the mainspace article, which is what I like to do in these situations to avoid duplication. I think editors should be encouraged to work on the mainspace article and not the draft, so that everyone is using their time efficiently. –] <small>(])</small> 22:57, 31 December 2024 (UTC)
:Yes, bad idea. Sometimes it's reasonable to resubmit without changes if the decline was incorrect or the submitter has clarified something. <span style=white-space:nowrap;>] <span style="background-color:#e6e6fa;padding:2px 5px;border-radius:5px;font-family:Arial black">]</span></span> 16:06, 10 November 2024 (UTC)
:::::I was reverted. {{u|NatGertler}}, can you please elaborate on how you plan to move a draft over an existing mainspace page? Did you perhaps mean that you plan to manually copy paste merge some pieces of the draft instead? In which case, the draft would be fine as a redirect, since the page history can easily be checked. –] <small>(])</small> 23:52, 31 December 2024 (UTC)
::How about a bot that could add a Comment to the submission to let the submitter know that the submission has not changed and that they could continue working on it? ] (]) 16:39, 11 November 2024 (UTC)
::::::If you look at the AfD, there is reasonable support for (if the article survives AfD) deleting the version that is currently in mainspace and moving this draft one into mainspace at the same address. This version is in much better shape, and there is nothing substantial in the mainspace one that needs to be merged into this. If folks are to work on either of them, we want them working on this one, which is likely to be the surviving version in some form (whether it survives as a draft or in mainspace depends on the outcome of the AfD, but even at the most complicated take it will be merged into the mainspace one, so may as well have it here.) -- ] (]) 01:10, 1 January 2025 (UTC)
:I agree having any kind of auto-decline bot is a bad idea. However, simply putting them in a list, like ], sounds reasonable. It would be useful for finding easy declines/accepts, provided that the reviewers check the circumstances behind the resubmission. ] <i><sup style="display:inline-flex;rotate:7deg;">]</sup></i> 16:38, 10 November 2024 (UTC)
:::::::Got it. I think this should be de-duplicated at some point, but with your comment in mind, I suppose it's OK to wait until after the AFD is over. –] <small>(])</small> 01:26, 1 January 2025 (UTC)


== ] is live! ==
* I like the idea of a bot that can at least note the absence of material change to a resubmitted article. ] ] 21:58, 10 November 2024 (UTC)
*:{{ping|BD2412}} Let's say software detects that a submission has not changed (much) since the last time it was submitted. What should it do? Message the submitter? Stick a template on the submission? Stick it on a list similar to ]? Notify the previous reviewer? Something else? You can choose more than one option. ] (]) 10:54, 12 November 2024 (UTC)
*:: Notify the submitter and put a note on the submission to the effect that the submission was previously rejected, and that the reasons for the previous rejection should be reviewed prior to acceptance of the submission. Creating a list of little-changed re-submissions is also not a bad idea. ] ] 14:42, 12 November 2024 (UTC)


Per the outcome of ], which is shown above, and a request filed at ] by ], the above page is now live and ready for reviewers to use, maintained by ]. It's actually caught 1 already in only the couple hours its been live, see ]. :)
===RfC: Should a bot be created to handle AfC submissions that haven't changed since the last time they were submitted?===
<!-- ] 19:01, 20 December 2024 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1734721271}}
Should a bot be created to handle AfC submissions that haven't changed since the last time they were submitted?
* '''Option 1''': Yes. The bot should automatically <s>reject</s> <ins>decline</ins> any such submissions.
* '''Option 2''': Yes. The bot should add such submissions to a list, similar to the ].
* '''Option 3''': Yes. The bot should notify the submitter and comment on the submission.
* '''Option 4''': Yes. The bot should add such submissions to a list '''and''' notify the submitter and comment on the submission.
* '''Option 5''': No.
]<sub>]<sub>]</sub></sub> (]/]) 18:55, 15 November 2024 (UTC)


There's also a hosted on Toolforge to look up an article and see if it's resubmitted without changes, if that's more your thing.
Note that I changed Option 1 to decline rather than reject, as reject is a very specific term in AFC and I don't think that is what was meant here. Reject means the draft can never be resubmitted, due to violating ] or having extremely obvious and egregious non-notability. –] <small>(])</small> 22:07, 16 November 2024 (UTC)


For adding an item to the list, the requirement is that it has an AFC submission wizard edit, directly after an AFCH decline.
-----


For removing an item from the list, the requirement is that it has a edit that is not done with AFCH or the AFC submission wizard (note: it's been very kindly suggested by ] that it should maybe do some detecting to see if a edit is meaningful or not, any suggestions for when/when not a edit counts as meaningful are most welcome!)
*'''Oppose option 1''', per the discussion above this is a very bad idea. '''Support option 2''', this seems harmless and seems worth tracking - as long as it is made absolutely clear that being rejected previously is not a reason to reject - if the original reason was correct and still applies then it can be rejected again for that reason. '''Neutral''' on the other options, but any comment/notification ''must'' make it clear that it is informational only and not a rejection. ] (]) 19:21, 15 November 2024 (UTC)
*'''Option 5'''. AfC reviewers make mistakes. We should not be prejudicing someone's future AfC chances based on those mistakes any more than we already do - namely, that there is already a gigantic decline message on the draft. AfC is frequently a dispiriting, demoralizing, and baffling experience for new editors, mostly one of waiting and then receiving templated replies they do not fully understand. I oppose this, and I oppose any other efforts that would further increase new editor alienation in this way. -- ] (]) 19:29, 15 November 2024 (UTC)
*Option 4, but as with Thryduulf, the comment on submission should be marked as informational and a reviewer will come by to assess the submission. ] (]) 19:27, 15 November 2024 (UTC)
*'''Support option 2'''. Whether any changes have been made since the last decline is often something I look for when reviewing an article with declines, as it helps to see if the concerns from that last decline were addressed (if I feel like they are appropriate to the article as I see it), and this would be a benefit to a reviewer without being additionally "punishing" to a new editor. ]] 19:47, 15 November 2024 (UTC)
*Speaking as someone who doesn't review drafts but very occasionally comments on them, I think an {{tl|AfC comment}}-like mention at the top would be easiest to work with, so I guess I'm at Option 3 or 4. Very dubious that a bot could reasonably handle the "(much)" in the preceding section header without unacceptable false positives ''and'' negatives, but detecting ''completely unchanged'' submissions would be both feasible and useful. —] 20:01, 15 November 2024 (UTC)


Please don't hesitate to reach out to me if you have any feedback for this bot task, or would like anything changed about it. Thanks! :) ] <sup>]]</sup> 06:25, 1 January 2025 (UTC)
*'''Support Option 5''' - No. '''Oppose Options 1, 2, 3, 4'''. Support based on ]'s comment. Opposes are my own, doubtless with others. As a reviewer I declare myself capable of checking, and I do. 🇺🇦&nbsp;]&nbsp;]&nbsp;🇺🇦 20:43, 15 November 2024 (UTC)
*'''Option 4''' but instead of adding to a list, add to a category (preferably a hidden one). Yes, definitely notify the submitter and comment on it, but having a list may discourage the submitter if they see that their draft is listed on a list. Having a hidden category would be better (at least imho) where a parameter of ] can add the draft into the category. ] <big>(]</big> · <small>])</small> 20:49, 15 November 2024 (UTC)
*:Though with all options, the reviewer would still do the same work... ] <big>(]</big> · <small>])</small> 20:50, 15 November 2024 (UTC)
* I suppose I wouldn't oppose a bot that automatically leaves a comment, but I don't really see the point either. Reviewers should be evaluating based on the current state of the draft — previous declines really shouldn't matter in most cases. I think this would encourage summary "no change" declines without actually looking at the content of the draft. <span style=white-space:nowrap;>] <span style="background-color:#e6e6fa;padding:2px 5px;border-radius:5px;font-family:Arial black">]</span></span> 20:56, 15 November 2024 (UTC)
*:You're right. It would encourage reviewers to "decline" the draft just because it hasn't changed since last review. However, thinking now, it ''might'' encourage editors to keep working on the draft because they see that "it hasn't changed since last review". If that's the case, reviewers should "wait". So perhaps after the bot leaves a comment, reviewers should wait at least a couple minute before reviewing in case the editor wants to add content? ] <big>(]</big> · <small>])</small> 21:03, 15 November 2024 (UTC)
*::My position is that if they did not see ''being declined'' as reason to keep working on the draft, they are unlikely to have a positive view of an automated message telling them that the draft hasn't changed. -- ] (]) 21:07, 15 November 2024 (UTC)
*'''No''' too easy to game. The simplest bot would just compare revisions. A submitter would then just have to add like a space or a few words to change it. A more complicated bot would flag changes that were too small or simple, but then that just encourages submitters to ramble. A bot can't assess the quality of a change, only editors can. ] <sup>]</sup>] 21:01, 15 November 2024 (UTC)
* '''Strongest Oppose to 1''' as bad reviews do exist. Also, sometimes submitters have discussed it with the reviewer and been told to resubmit for a second opinion etc.
:'''Weak Oppose 2, 3 & 4''' as I'm not convinced a bot will accurately determine what no substantive change is and I see little value in just flagging straight re-submits
:'''Support 5''' as de-facto option left ] (]) 21:20, 15 November 2024 (UTC)
*'''Option 2 or 4''' especially with several disruptors (and one dynamic IP so block doesn't help) who just do drive by submissions. Frustrating to the editor to receive another decline through no fault of their own. Having them in the queue is a waste of reviewers' time though when it's a quick decline because the improvements haven't been made. I think it's less wrong decline and more no discussion about why the feedback was wrong that's the red flag. ] ] 23:34, 15 November 2024 (UTC)
*:I lean towards '''Option 5''', but for those pages/editors engaged in a problematic level of drive-by submissions, I wonder whether a completely different approach might work better. For example: If you think the previous decline was correct, and you also think it's a drive-by re-nom, then move the article to the mainspace and send it straight to AFD. If it's kept, then the submitter was correct, and the previous decline was wrong. Also, it's now out of the AFC queues. However, if it's deleted, ] the page name(s) in both Draft: and mainspace for the next year (or two?), so that AFC can be done with it. Either way, it's no longer AFC's problem. ] (]) 05:22, 16 November 2024 (UTC)


:Also btw an API is also available by sending a GET request to https://molecularbot2.toolforge.org/resubAPI.php?pageName=test, replacing test with the name of the page, excluding "Draft:"! :) ] <sup>]]</sup> 06:26, 1 January 2025 (UTC)
:'''Strongly oppose Option 1'''. Frankly, trusting fellow reviewers to check how much a draft has changed since a previous decline is reasonable to do. Letting a Bot do something creates an option to game the system. We don't need that. --] (]) <small>(]) (])</small> 00:37, 16 November 2024 (UTC)
:Thanks for implementing the bot—on the new year nonetheless! ] <i><sup style="display:inline-flex;rotate:7deg;">]</sup></i> 13:47, 6 January 2025 (UTC)
:Support '''Option 2''', neutral on Option 4, and oppose the rest. I do not see the point in notifying submitters when they already are aware they did not make any changes. Perhaps they wanted another review. Putting unchanged drafts in a hidden list like the copyvio one seems optimal as it reduces complexity and unnecessary messages to submitters. It would make finding easy declines and disruptive drive by submissions easier to find. I also support adding a verbiage that being unchanged should not be the sole reason to decline again. ] <i><sup style="display:inline-flex;rotate:7deg;">]</sup></i> 00:57, 16 November 2024 (UTC)
*'''Option 5''' - Reviewers should be instructed, more clearly if necessary, to check whether the draft has been revised since the last decline, and to use human judgment in deciding what is enough improvement. There is no need for automated aid, which could make mistakes and could be gamed. ] (]) 06:10, 16 November 2024 (UTC)
* '''Option 2''', at least, '''option 4''', at best. Yes, reviewers make mistakes, but they make mistakes in both directions, and should also consider the guidance inherent in a previous rejection. ] ] 15:16, 16 November 2024 (UTC)


== Trying out using Microsoft Copilot to discuss notability of a particular topic ==
:'''Option 4''' preferably, but I'm okay with '''option 5''' as well (TBH, I don't think this is a major problem in the bigger scheme of things, and the details could be tricky). Also '''oppose option 1''', regardless of whether it was intended to say 'reject', or merely 'decline'. -- ] (]) 15:29, 16 November 2024 (UTC)
::PS: When I say details could be tricky, I didn't mean in a technical sense, but rather in defining what the trigger condition of "changed (much)" actually means. Size change doesn't always tell us much: only a few kb might have changed, yet the draft was completely rewritten; conversely, a large kb change could mean that the author simply deleted the earlier AfC templates. Number of sources, ditto: adding ten new rubbish sources to the earlier rubbish sources still adds up to only rubbish; whereas using the same sources but citing them correctly might have resolved the decline reason. -- ] (]) 15:39, 16 November 2024 (UTC)
*'''Option 5'''. AfC reviewers sometimes make mistakes, particularly when dealing with areas that they are not familiar with. (I can't count how many drafts on academics have been rejected and told to supply GNG, and I've also seen rejections of drafts on politicians that clearly passed NPOL.) Creators should always be allowed to ask for a second opinion. ] <small>(])</small> 18:52, 16 November 2024 (UTC)
*'''Option 5''' Per asilvering and Espresso Addict. I would further that; reviewers ''often'' make mistakes....specifically declining articles for reasons that are not decline criteria. Also some reviewers tend to pass only unusually safe passes. <b style="color: #0000cc;">''North8000''</b> (]) 18:43, 19 November 2024 (UTC)
*'''Option 5''' per Asilvering. If a reviewer makes a mistake (which often happens), the submitter shouldn't be even more penalized for it. Same if they just want another opinion on their draft. ] (] · ]) 18:52, 19 November 2024 (UTC)
*'''Option 2 or 4''' per Star Mississippi. I'll add: Resubmitting an unchanged draft is a sign of a problem even if the declining reviewer had made a mistake. And it will rarely be the case that they have made a mistake given a creator who resubmits an identical draft, which very strongly correlates with the draft being poor in the first place and not deserving of acceptance.—] 13:04, 20 November 2024 (UTC)
*'''Option 5''' (do nothing). Like Primefac below, I'm surprised this got the RfC stage given the overwhelmingly negative reception in the original discussion, and hope the closer of this discussion will take that into account. AfC reviewers make mistakes but, more to the point, people can have good faith disagreements about the suitability of an article. If the submitter disagrees with a reviewer, they have every right to ask for a second opinion without edit warring with a bot or making pointless changes. &ndash;&#8239;]&nbsp;<small>(])</small> 08:20, 25 November 2024 (UTC)
*'''Option 2 or 5''' - Given the unevenness of reviews, authors have legitimate reasons for seeking a second, third or fourth review. ~] (]) 15:55, 30 November 2024 (UTC)


I'm not sure if people have tried this out or not. I searched AfC talk archives for , , , and I saw that people have been talking about AI generated submissions, but I haven't seen any discussion on doing something like this.
===RFC discussion===
Um... didn't this get fairly roundly shot down in the original discussion? Why does it need a full RFC to work out any further details? ] (]) 19:41, 15 November 2024 (UTC)


So, anyway, I'll seek to share the dialog:
:I think that only Option 1 was outright rejected in the above discussion. The rest were counterproposals that seemed to have at least some support. ]<sub>]<sub>]</sub></sub> (]/]) 19:48, 15 November 2024 (UTC)
::Meh, RFC just seems like a lot of bureaucracy for something that didn't really have a lot of discussion and could have probably been dealt with in-house. Carry on I suppose. ] (]) 19:49, 15 November 2024 (UTC)
:::I second your 'meh'. Why are we going through this extra layer. ''If it ain't broke don't fix it!'' 🇺🇦&nbsp;]&nbsp;]&nbsp;🇺🇦 20:45, 15 November 2024 (UTC)
::::Hate to be Devil's Advocate for an RFC I've opposed, but I think we've got more, clearer answers to the question in the few hours since this RfC opened than we had in the entire earlier discussion, so there's that. And I do think AfC is pretty broke and needs some fixing. I just think this is tinkering in the wrong direction. -- ] (]) 20:49, 15 November 2024 (UTC)


https://github.com/davidkitfriedman/general/blob/main/2025_01_02_dialog_with_Copilot_on_notability_of_GlobalProtect.md
While we're here and talking about reviewers making mistakes, let me make my perennial plea that, if you see, this, you go ask the reviewer about it on their talk page. We all have to learn somehow! And if the reviewer is making lots of mistakes, it will be easier for any single editor to figure this out later if there's a track record of them on their talk page. By the way, for those who haven't learned this trick yet: the AFCH script will allow you to resubmit drafts ''as though you were the original submitter''. If you think something was inappropriately declined, you can resubmit it to the queue yourself and then immediately accept it, or resubmit it and leave a comment explaining why you did so. -- ] (]) 21:45, 19 November 2024 (UTC)


I asked Copilot to argue against notability for ], and then also to argue for notability.
:Or if you want to resubmit a draft on behalf of another user so they get the AfC communications rather than you, such as the Accept notification, you can use <nowiki>{{subst:submit|Creator's username}}</nowiki>. The other option is to click the Resubmit button then change the User (u=) from your name to theirs. ] (]) 22:34, 19 November 2024 (UTC)
::The AFCH script will do this for you automatically. -- ] (]) 22:56, 19 November 2024 (UTC)
:::Ahh..ok, I see now. You review on an already declined draft. I had never clicked the Submit button because I assumed it worked the same way as the Resubmit button in the decline message but the AFCH script gives you options to assign the submitter. I can't tell you how many times I have resubmitted drafts using the manual methods I outline above. ]! :) ] (]) 23:27, 19 November 2024 (UTC)


Initially I just asked it what are some of the major consortia that Google is a part of.
== Master log? ==


Copilot responsed and then also prompted with, "Is there a specific area of Google's partnerships you're particularly interested in?".
Is there a log of AfC-everything – submissions regardless of whether they've been reviewed or are pending, reviews regardless of the outcome and the reviewer, the whole shooting match? And if so, is this log searchable, if I wanted to know, say, whether anyone has submitted a draft with a particular word in the title (or better yet, title or content)? -- ] (]) 13:43, 2 December 2024 (UTC)
:The short answer is, as far as I am aware, no. We have categories for every page submitted that is still undeleted (part of the reason why we put AFC tags on the talk pages) and we have {{t|AfC statistics}}, but nothing like a database report of ''everything''. ] (]) 15:15, 2 December 2024 (UTC)
::I believe @]'s bot (which updates the {{t|AfC statistics}}) maintains a (private?) database on toolforge which has more details than what is saved to the template, though even that may not contain ''everything''. – ] (]) 20:03, 2 December 2024 (UTC)
:No but you can use the categories as Primefac says such as searching {{tq|incategory:Pending_AfC_submissions}}, {{tq|incategory:Declined_AfC_submissions}} or {{tq|incategory:Draft_AfC_submissions}} in the draft and user spaces but that wont show you the deleted or accepted. While the Accepted articles talk pages are mainly in ] I'm not aware of any "talkpageincategory:" search facility so it does not help. You can also search all three cats with {{tq|insource:/\{\{AfC submission\|/}}, but since that is most drafts often just searching draft space is easier as it also won;t catch the oddities such as {{tl|AfC_submission}} with an underscore. ] (]) 15:47, 2 December 2024 (UTC)
::Could also use ] to combine cats and title searches in various namespaces. ] (]) 16:52, 2 December 2024 (UTC)
::While there's no "talkpageincategory:", there does exist , added 11 days ago (]). – ] (]) 20:11, 2 December 2024 (UTC)
:::oh! nice! Good work ] ] (]) 20:14, 2 December 2024 (UTC)
:On the hunt for socks? If the "content" you're looking for is an unusual URL, https://spamcheck.toolforge.org/ will do you. -- ] (]) 22:28, 2 December 2024 (UTC)
:If you ask a more specific question, we can probably craft a ] for you. For example, "any page currently in draftspace containing the word Bob". –] <small>(])</small> 23:12, 2 December 2024 (UTC)


And so I told it why I had asked the question initially, and it cited Misplaced Pages's policies, and then asked, "Do you have a specific consortium in mind that you're researching?"
== ] ==


I could mention that I did see this mentioned in ], so perhaps editors don't feel that it's necessarily worth discussing with LLMs whether a particular topic meets notability or not.
I need some help with this review. I'm having a hard time establishing whether the sources make this subject notable. <span style="font-family:monospace; font-weight: bold"> <span style="color:ForestGreen;font-size:15px"> ]</span> (<span style="color:#324c80">she/they</span> | ]) </span> 04:24, 3 December 2024 (UTC)


<blockquote>
:@] {{declined}}, with a full rationale. Some ''might'', but I sample checked a significant number and each, chosen as randomly as I was able, failed as a reference.
When exploring AI techniques and systems, the community consensus is to prefer human decisions over machine-generated outcomes until the implications are better understood.
:Good call asking for other eyes. 🇺🇦&nbsp;]&nbsp;]&nbsp;🇺🇦 05:55, 5 December 2024 (UTC)
</blockquote>


] (] · ]) 05:11, 3 January 2025 (UTC)
== Help desk new question page ==
:Meh... what people choose to do on their own time to not think for themselves is their own concern; if an LLM tells someone that a subject is notable, but the subject is not notable, we're no worse off than the Fiver writers that get paid to write shitty prose about non-notable grocery store owners. If the LLM tells the editor that a subject is notable, and they ''are'', then all they've really done is waste their own time, since the subject would pass our criteria anyway. ] (]) 07:05, 3 January 2025 (UTC)
:LLMs do not think in the traditional human way because that's not what they're trained to do. Their job is to provide compelling output. The problem with that is that LLMs don't know what truth or factual accuracy is, i. e., they don't know if what they've just made up makes any sense. In a nutshell, discussing with an LLM is like talking to a parrot on steroids. --] (]) <small>(]) (])</small> 08:20, 3 January 2025 (UTC)
:I've seen several editors assuring us that their obviously LLM-generated draft has been painstakingly written to comply with all Misplaced Pages requirements for notability, verifiability, and other core policies yada yada... and then it turns out the said draft doesn't cite a single source. So if the editor hasn't the first clue about our requirements, then the LLM clearly won't impose one on them. -- ] (]) 08:39, 3 January 2025 (UTC)
:LLM and Misplaced Pages don't mix very well. In my opinion, in almost all cases, it's just a timesink. LLM is useful for certain non-Misplaced Pages things, but is not a great fit here. –] <small>(])</small> 17:38, 3 January 2025 (UTC)


== African legislators ==
I often see the same editor asking multiple questions @ the help desk and they are often told not too by others, sometimes in a bitty way. I wondered why so may did this and I think the reason is the userpage decline template links to ] with the draft title filled in but it seems non-obvious, for new editors, how to get from this page to the help desk without posting a new question. Should we add a something like "If you have already asked a question about this draft recently please continue that discussion at the help desk ''']'''" to the top? ] (]) 14:49, 3 December 2024 (UTC)


Just found out why we're seeing so many new drafts (mostly very short stubs) on legislators, esp. Nigerian ones, lately: https://meta.wikimedia.org/Event:African_Legislators_in_Red This runs until the end of the month, and one of the rules is that the articles must get into the main space by then, so expect to see some fast track requests at the help desk as the deadline approaches... -- ] (]) 08:21, 4 January 2025 (UTC)
:Ah, that could indeed explain this. (I always assumed it was because users didn't realise it's a threaded forum, and not a chat stream etc.) That seems a good suggestion; worth a try.
:And one of my new year's resolutions will be to make an effort to be less "bitty" to those opening multiple threads, now that I know why they do it. -- ] (]) 15:02, 3 December 2024 (UTC) :Ugh. People can wait. We don't expedite for contests. ] (]) 13:53, 4 January 2025 (UTC)
::I'm not sure I fully understand what's happening here, could someone provide a diff/example of this happening? ] (]) 20:19, 3 December 2024 (UTC) ::hmm... I guess we do. Vanderwaalforces (intentionally not pinged) seems to be participating and reviewing drafts from this thing. ] (]) 15:04, 4 January 2025 (UTC)
:::So long as it's individual reviewers making the offer to do it, seems fine to me. Not really different from someone, say, going through and reviewing all the OKA drafts (I've done this) or volunteering to help out with an editathon as a reviewer (I've done this, too). But I vote we ping Vanderwaalforces to each and every help desk request, if they arise. :P -- ] (]) 16:15, 4 January 2025 (UTC)
:::Some editors keep opening new questions on the help desk rather than continuing with one that's ongoing, often one after another. So I'm proposing that these may be the editor coming back to the help desk from the link on the decline on the users talk page. That goes to a page like and I'm saying that it encourages asking a new question everytime and many would not see or understand using the breadcrumb link to the help desk at the top. ] (]) 09:45, 5 December 2024 (UTC)
::::Please do ping me if need arise! ] (]) 16:21, 4 January 2025 (UTC)
::::Why don't we adopt the pragmatic solution of not worrying, and answering questions as they arise, but tidying up sweetly prior to answering?
::::Oh, sure, I don't have any issue with them (or anyone else) making it a personal priority to help out, I'm just saying we-as-a-Project should not be expediting things. ] (]) 16:23, 4 January 2025 (UTC)
::::Unless, of course, someone writes a gadget so we can highlight threads to merge, and we do that? 🇺🇦&nbsp;]&nbsp;]&nbsp;🇺🇦 09:52, 5 December 2024 (UTC)
:I've been accepting a lot of these as inherently notable since I tend to camp out on the recently submitted feed but, yeah, I don't see why these endless stubs need to go through AfC..? <span style="background-color: RoyalBlue; border-radius: 1em; padding: 3px 3px 3px 3px;">''']''' <small>]</small></span> 15:34, 4 January 2025 (UTC)
:::::I have ignored for years but after seeing it again a couple of times recently I engaged brain to wonder why it was happening. Updating the gadget to work out if there is an active question is a nice ideal solution but too much work for the problem. Is it not better to tell editors they can continue a discussion rather than open a new question rather than give give them an interface that encourages it then tell them they are wrong. Just adding a simple explanatory sentence and link seemed like a quick, simple easy solution..... ] (]) 10:13, 5 December 2024 (UTC)
::Wait, they get money for this? I didn't think that was permitted? <span style="background-color: RoyalBlue; border-radius: 1em; padding: 3px 3px 3px 3px;">''']''' <small>]</small></span> 15:34, 4 January 2025 (UTC)
::::::Ah, I see, something like ]. I see two (maybe three) options here. First, we change nothing and politely merge/combine duplicate sections. Second, we make the decline link a direct link to the HD and ''hope'' that editors use the "Ask a new question" link at the top if they have a question (which, if I recall, did not work, and the whole reason we have the script in the first place). Third, we could add an additional line as proposed, saying that existing questions will be answered without a new question not needing to be filed. ] (]) 13:13, 5 December 2024 (UTC)
:::Based on what I could find (which was little more than ]) it appears above-board, since they're not being paid to edit anything specific. ] (]) 15:42, 4 January 2025 (UTC)
:::::::Yes that is the sort of thing that happens most, but I failed to find a diff for one of the cases of more than 2 or the sometimes bitty remarks not do do it. Not that I hang about the HelpDesk much. On the current page GwnftLight and Sukdev Mahapatra also had two back to back posts. ] (]) 13:23, 5 December 2024 (UTC)
:I added a variant of that text to the top - feel free to copyedit. ] (]) 13:45, 7 December 2024 (UTC) ::It's probably their way of having a check/balance for the stubs so that they don't have the issue that some other editathons have had where people spam utter garbage and ''maybe'' it gets reverted. ] (]) 16:00, 4 January 2025 (UTC)
:::@] Correct! ] (]) 16:23, 4 January 2025 (UTC)
::Oops. It seems the script replaces it altogether. Will need a script update as well. – ] (]) 13:47, 7 December 2024 (UTC)
::@] They actually need to go through AfC as a "damage control" both for English Misplaced Pages and the project itself. Also, these editors are mostly new, so yeah! ] (]) 16:23, 4 January 2025 (UTC)
:::{{fixed}} – ] (]) 15:33, 7 December 2024 (UTC)
:::Makes sense :) <span style="background-color: RoyalBlue; border-radius: 1em; padding: 3px 3px 3px 3px;">''']''' <small>]</small></span> 16:24, 4 January 2025 (UTC)
::::Thanks SD0001 ] (]) 15:35, 7 December 2024 (UTC)
:Most of them are easy to accept. I haven't come across too many issues (which is uncommon for contests with rewards), though some of the longer drafts do tend to lean on the promotional side. I've also found at least 3 copyvios stemming from this event from unrelated Copypatrol work, so be on the lookout for that I guess. <span style="padding:2px 5px;border-radius:5px;font-family:Arial black;white-space:nowrap;vertical-align:-1px">] <span style=color:red>F</span> ]</span> 17:55, 4 January 2025 (UTC)
::@] Oh yes! I, in fact, ] for copyvio. I am especially not taking that lightly. By the way, I cannot thank you enough for keeping an eye on the article and tagging them with the WikiProject template, kudos! ] (]) 18:02, 4 January 2025 (UTC)


== Draft nominated for ] as not notable after decline ==
==J-1 visa ''vs ''J-1 visa==
I declined ] as a duplicate of ], however, ] (I think) indicating they are different topics and I should re-review the draft. To be honest, I don't entirely understand. Given my lack of understanding, would someone else mind taking a second look at both the editor's comment to me and the draft and, if appropriate, remedying any error I've made? I may be missing something. Thanks. ] (]) 15:49, 3 December 2024 (UTC)
:It looks like this might be one of ] of the J-1 visa? ] (]) 20:21, 3 December 2024 (UTC)
::Yeah, I was going to say the same. Mind you, it's been years since I've dealt with any US visa issues, so could be some newfangled stuff I don't know about. In any case, don't see why different flavours of J-1 (or even J-class) would require separate articles? -- ] (]) 20:40, 3 December 2024 (UTC)
:::The draft does get rather far into the weeds of the specifics of that visa type. The article is pretty long as it is, though, so a full merge might not make sense. ] (]) 20:42, 3 December 2024 (UTC)


A draft ] on a politician who does not meet ] was declined, and then nominated for deletion by the reviewer who declined it. It was my understanding that AFC reviewers should know that ]. Either an AFC reviewer has been given access to the script who hasn't been adequately briefed as to how drafts are reviewed, including that they are only nominated for deletion in rare circumstances, or an editor who is not an AFC reviewer is reviewing drafts. Do the guidelines for reviewers need clarifying? We know that sometimes New Page reviewers mistakenly review new drafts with the same standards as they use to review new articles, but apparently some AFC reviewers also don't know when t not to send drafts to XFD. ] (]) 06:44, 5 January 2025 (UTC)
== ] ==


:Or it could just be that the reviewer didn't know, and they could be gently told how to do it correctly. ] <sup>]</sup>] 07:38, 5 January 2025 (UTC)
I am reviewing ], and I have two mostly unrelated questions. The first is about reviewing a draft when the title in article space is a locked redirect. This is a question that I have asked before, but the answer has not always been entirely clear, and I would rather ask again than not ask and make a mistake. The title is a locked redirect because there was a previous AFD (the third AFD) and the consensus was to redirect and salt. Am I correct that I should compare the draft against the deleted version in the history, and consider whether there has been enough of a change so that it is reasonable to consider making a request to ]? If so, my thought at this time is that it is not much of a change, and the submitter has not met the burden of overcoming the consensus of the AFD, but I will review it one more time. Are there any particular rules that I should follow when reviewing a draft where the title is a locked redirect due to an AFD? ] (]) 20:42, 3 December 2024 (UTC)
:Short answer: yes. If the draft isn't significantly different, then it's not worth accepting. ] (]) 20:46, 3 December 2024 (UTC) ::I wouldn't necessarily call this a "hidden" rule or anything but I agree with Eek that "they didn't know" is probably the most likely scenario, and they should politely be a) informed, and b) asked to withdraw the MFD. ] (]) 07:58, 5 January 2025 (UTC)
:Context: ]. –] <small>(])</small> 11:10, 5 January 2025 (UTC)
::I declined the draft. This is a case of ]. ] (]) 05:17, 4 December 2024 (UTC)
::I left the MFDer a message at their user talk about not MFDing drafts like this one in the future. They were receptive to the feedback. –] <small>(])</small> 11:51, 5 January 2025 (UTC)


== ] ==
===Mostly Constructive Edit with Vandalism===
The second question has to do with one of the edits to the draft. The edit appears to have been mostly constructive, but it introduced sneaky vandalism to an item in the infobox. I have reverted the vandalism and warned the editor. Should I be satisfied with assuming that the other edits were constructive, or should I revert the entire edit? I would have reverted the entire edit, except that there had been a subsequent edit that appeared to be constructive. What should be done if one discovers that an edit was mostly constructive but made a destructive change? ] (]) 20:42, 3 December 2024 (UTC)
:If there's a mix, and it's not obvious what was good and what was bad, I'll revert the whole thing. That's just my philosophy, but I'm not going to untangle a complex edit if "vandalism" is part of it. ] (]) 20:46, 3 December 2024 (UTC)
::Yes. The only reason that I didn't revert the whole thing is that there had been another edit after it. It now appears that the change may have been a sloppy error rather than vandalism. The editor changed the height of the subject from 2 m to 2 cm. 2 m is 6 ft 7 in, which is what the subject's height has been reported as. The two possible explanations are both implausible, either that it was sneaky vandalism or that it was an error, so ] applies. So I think that the draft is now correct. If the subject becomes individually notable in the future, his height is likely to be 201 cm or 202 cm. ] (]) 05:15, 4 December 2024 (UTC)


is linked on the header, but I believe serves no purpose. This vaguely-named page doesn't have any "list" of submission by itself but links to two other lists. One of them, ], is already linked to by the header.
== drafts are too long ==


I propose it to be merged to its parent page /Submissions to reduce confusion and the clutter in the header. Only thing that really needs to be merged is the mention of ]. ] <i><sup style="display:inline-flex;rotate:7deg;">]</sup></i> 14:00, 6 January 2025 (UTC)
Please see discussion: ]. -- ] (], ]) 00:58, 9 December 2024 (UTC)
:Hasn't worked since ]; you're just the second person to notice. Feel free to pull whatever you need from the history and plonk it elsewhere if that makes sense. ] (]) 14:25, 7 January 2025 (UTC)


==A little merging issue==
== ] ==


Hello. Following a personal request for an AFC, I thought I would give it a try in spite of an article already existing as a redirect (never did). I over estimated my skills and need a little help :)
This draft seems on the edge of violating ] to me, especially since its author has a 16-year history of anti-water fluoridation POV-pushing, but I'd like another pair of eyes to determine if this article may be acceptable. ]<sub>]<sub>]</sub></sub> (]/]) 21:47, 15 December 2024 (UTC)
:At the very least, I'm not seeing any evidence of notability there. And for the coverage that does exist outside of the very recent court case, it's certainly not positive coverage. Which isn't reflected in the article as it is currently. And that does seem like an NPOV problem. ]]<sup>]</sup> 21:52, 15 December 2024 (UTC)
::See also ]. The draft doesn't persuade me that anything has changed in twelve years except the government in Washington. ] (]) 00:36, 17 December 2024 (UTC)


So the old article was a redirection (]). I removed the redirection. Could not "Yes" the draft article under the right name (]) becase of the already existing article. Thought I could approve it under a different spelling ] and then merge their histories.
== Indian state symbols ==


Ok, histories are not . What am I missing ? ] (]) 14:09, 6 January 2025 (UTC)
It seems we have a new instalment in the series of bogus Indian state symbols, this time with ]. Different IP from the previous ones, but probably the same user. Just flagging this here to avoid a repeat of the earlier sich. -- ] (]) 12:41, 17 December 2024 (UTC)
:I don't even understand, maybe because I am thinking about a lot of things. It does appear that Primefac <s>has done something like that</s> cleared the issue. Cheers!<span style="font-family:Papyrus; color:#800080;">]</span><sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 08:54, 7 January 2025 (UTC)
::<s>Anthere, there are a couple of other things you should have done.</s> <ins>For anyone who isn't an admin, this is what should have been done</ins>
::*Request a {{t|db-afc-move}} on the redirect {{small|(this might have been declined given the old article's history, but then I -- as an admin -- would have probably just done a page swap)}}
::*Request a page swap at ]
::<ins>For an admin, the options are:</ins>
::*<ins>Pageswap the draft and article</ins>
::*<ins>Move the old page (without redirect) to a disambiguated title</ins>
::Copy/pasting a page to another location is not a good way to get a page to a specific title. Just to clear up SafariScribe's confusion, I just did a page swap on the two pages to put the new article at the correct title, while preserving the history of the old page.
::<s>As a minor note, ] is only available to admins, which is why you couldn't use it.</s> ] (]) 13:52, 7 January 2025 (UTC) {{small|Struck, updated, and inserted: 14:07, 7 January 2025 (UTC)}}
:::I think Anthere is an admin. Is showing blue in my user highlighter script. –] <small>(])</small> 13:54, 7 January 2025 (UTC)
::::I was just going to say. And on multiple projects, it seems. -- ] (]) 13:55, 7 January 2025 (UTC)
:::::''le sigh'' Forgive me for not having special admin-script glasses on.
:::::A histmerge wasn't possible because there are (effectively) parallel histories; there was nothing that could be merged from the new page into the old page because of diffs from 2010 at the old page blocking the 2025 edits from the new. ] (]) 14:04, 7 January 2025 (UTC)
::::::This explains that... I felt vastly stupid :) Indeed, I could have swapped the two versions to have the new article history sitting at the right title. But I was trying hard to maintain both histories, which in fact was not really needed. Hmmm.
::::::Situation is perfect now. Real author of current version is credited. All good. Thanks a lot for fixing. ] (]) 20:27, 7 January 2025 (UTC)
:::::::Always happy to help, feel free to drop me a line any time you have histmerge questions, there are some who would say I'm an authority on the matter :-) ] (]) 20:37, 7 January 2025 (UTC)


== Non-English drafts ==
:I have cleared up the rest of the related junk edits from ]. ] (]) 12:52, 17 December 2024 (UTC)
==question==
Hi I was just curious, I have done (alot, as I know other editors have as well) of AFC https://en.wikipedia.org/User:Ozzie10aaaa/AfC_log, I was wondering when the end of year awards (or recognition) for AFC are given?, thank you--] (]) 15:35, 20 December 2024 (UTC)


I've just declined yet another non-English draft (not the 1st one of the day, not even the 3rd, and that's just me!). In the ] there are nearly 1,000 such declines. Would it be a good idea to put something in the wizard to warn authors that this is the English-language Misplaced Pages, and if they want to submit content in another language they should head to the relevant language version instead? It's mildly annoying to review these drafts, but I can imagine it's much more frustrating to put in all that effort, only to be told ''afterwards'' that it was all for nothing. -- ] (]) 17:36, 7 January 2025 (UTC)
:@], what end-of-year awards are you talking about? I can't remember any, and I just checked the archives for December 2022 and 2023 and didn't see anything (but could have missed it). -- ] (]) 23:27, 20 December 2024 (UTC)
:Probably, but if they're non-English-speaking then what are the realistic chances that they're going to read yet another banner telling them they shouldn't create pages in languages other than English? I'd rather avoid banner bloat if possible, and if the subject is notable it's a quick thing to decline as non-Eng and let them (or G13) sort it out. ] (]) 18:16, 7 January 2025 (UTC)
::I assumed(hoped) that similar to NPP there would be some sort of award/barnstar for 2024,since the year is practically over, for all the AFC's done over the past year(for the editors)...--] (]) 23:55, 20 December 2024 (UTC)
::In my experience they're not all (or even most?) "non-English-speaking"; many do subsequently communicate in English at the help desk and/or talk pages, and some even resubmit an English-translated draft. It's just that many seem genuinely surprised that the different language versions are in fact separate projects, and that submitting a Bulgarian (say) draft here doesn't help get it into the Bulgarian Misplaced Pages.
::But yes, I take the point about banner bloat. Also, just because we warn them, doesn't mean they won't go against the warning regardless – after all, we get plenty of undisclosed COI/PAID submissions although the wizard clearly warns against these. -- ] (]) 18:29, 7 January 2025 (UTC)
:::Fair enough. As usual, I'm not strictly ''opposed'' to adding something, just that my knee-jerk reaction is to wonder whether it's worth doing so... ] (]) 18:31, 7 January 2025 (UTC)
: I am wondering how feasible it may be to have a bot detect the language being used, and send a note to that editor in that language. ] ] 16:29, 11 January 2025 (UTC)
::We have a number of non-English welcome templates, not sure a bot is needed, just a reviewer that doesn't mind taking an extra minute or two to leave one. ] (]) 17:44, 11 January 2025 (UTC)
:::Often, when I decline a non English draft, I use machine translation to provide a message to the creating editor about it. I suppose it depends on how often it happens regrind a bot. I somehow doubt a bot is needed. 🇺🇦&nbsp;]&nbsp;]&nbsp;🇺🇦 20:18, 11 January 2025 (UTC)
:Agreed with Primefac that banner bloat would be bad, but we could have the AfC submit wizard identify the language and add a banner only if it's not English. Wikimedia now has its own translation service (]), with includes a , so this can now be done without the privacy implications of using external services. – ] (]) 10:46, 24 January 2025 (UTC)
::{{Tracked in|https://github.com/wikimedia-gadgets/afc-submit-wizard/issues/8}}Created an issue in the tracker. Please do use GitHub to log other ideas and suggestions for the AfC submit wizard, which otherwise get lost in the archives of this page. – ] (]) 10:52, 24 January 2025 (UTC)


==Notified Jimbo instead of the user who submitted the draft==
::if there is a list of the top 20 AFC editors I would be happy to hand them out(below is a example)--] (]) 15:13, 21 December 2024 (UTC)
I accepted a draft created and submitted by an IP user, but the script actually Jimbo Wales instead of the IP user, I wonder what caused this? - ] (]) 09:11, 11 January 2025 (UTC)
:::I assume the NPP ones rely on the patrol logs. AfC does not have any central logging so there is no good data, especially for > 6 months when a lot of the declined drafts are deleted. ] (]) 15:16, 21 December 2024 (UTC)
::::Maybe ]? <span style="background-color: RoyalBlue; border-radius: 1em; padding: 3px 3px 3px 3px;">''']''' <small>]</small></span> 15:32, 21 December 2024 (UTC)
:::::If it had been running for a year I guess you could check the data from the last day of each month and add together but it's only been running since 12 November 2024. ] (]) 17:00, 21 December 2024 (UTC)
::::::this is better than nothing...]...I could leave the barnstar for all 100 ?--] (]) 17:57, 21 December 2024 (UTC)
:::::::I guess it's an approximation but not sure how it's getting its data but its a bit short. It says SafariScribe has 5418 reviews, but there log ] has 6846 entries. For myself it says 2889 reviews but my logs ] show 6200. I guess it does not count deleted items and I do a lot of 0 day junk bashing. ] (]) 18:22, 21 December 2024 (UTC)
::::::::well if there are no ''outright'' objections, I can do it Monday/Tuesday...--] (]) 19:30, 21 December 2024 (UTC)
:::::::::I see no harm and it's a bit of positive feedback which in the current world seems needed. So as far as I'm concerned go for it and thanks Ozzie for thinking of something positive. ] (]) 19:37, 21 December 2024 (UTC)
::::::::::,Ozzie--] (]) 14:52, 22 December 2024 (UTC)
for example ...
{| style="border: 1px solid gray; background-color: #fdffe7;"
|rowspan="2" style="vertical-align:top;" | ]


:@]: the submitting user the draft !ownership to Jimbo.
|rowspan="2" |
:Or possibly Jimbo created it himself. In which case, you should go and warn him against editing logged-out. ;) ] (]) 09:17, 11 January 2025 (UTC)
|style="font-size: x-large; padding: 0; vertical-align: bottom; height: 1.1em;" | '''The Articles for Creation Barnstar 2024 Top Editor'''
|-
|style="vertical-align: center; border-top: 1px solid gray;" | message
|}<!--template:AFC barnstar-->


== 2026 United States Senate election in ... ==
== Perhaps add to reviewing instructions? ==


Heads up: we've got five of these so far (see e.g. ]) and I suspect more are coming. I dunno if it's ] or not, but they look similar enough they can likely be accepted or declined as a group. ] (]) 00:20, 12 January 2025 (UTC)
Twice in the last week I've seen two AfCs passed which had previously AfD'd versions. Both of these AfC approvals were quickly tagged for G4. One of them had just been deleted at AfD and was under deletion review when the filer created a new draft which was miraculously reviewed in two days and quickly passed. This really screwed up the active DRV, which I was forced to close procedurally even though the filer had almost no support from commenters. What instructions do we give AfC reviewers about checking deleted edits and deleted versions from two days previously? Passing submissions which are currently at DRV? I'm aware that Articles for Creation is one approved way to recreate a deleted page, however this project surely has some guidance on the matter. Seems this should be on a checklist somewhere ("Is this namespace currently at a deletion process? Quickfail if yes."), checking a new draft against deleted versions. ] (]) 18:16, 20 December 2024 (UTC)


:I'd decline all unless if there are secondary sources actually discussing the state-level senate elections. ] <i><sup style="display:inline-flex;rotate:7deg;">]</sup></i> 11:27, 12 January 2025 (UTC)
:If the article is of the same name then the AFCH tool says if it was previously deleted and so that should lead reviewers to look at the previous reasons. Since the ] is to determine if it would be deleted at AfD checking the previous deletions should be a key point of any review. Personally I have always thought the previously deleted warning should be a bit larger and remind people to check. ] (]) 18:54, 20 December 2024 (UTC)

::Some reviewers might be concerned about readily being able to view previous deleted versions. As an admin, I'd be happy to spend a few minutes helping reviewers with temporarily undeleting such material. If I didn't possess the tools, I'd go to ] and ask to see the page temporarily before I approved the draft. I'd likely approve such a request 99% of the time. ] (]) 19:01, 20 December 2024 (UTC)
== ] ==
:::I disagree with KylieTastic about previous deletions needing be to more prominent than what they are already (well, I say I disagree but KylieTastic is usually right, thus their Tasticness, so likely I am missing something). When a reviewer clicks "Review", there is a popup that lists all the deletions of an article of the same title and the logged reason/notes (G11, AfD, etc.), which to me is very clear. I think this particular scenario is a one-off. Outside if extenuating circumstances or a mistake/miss, I cannot think of reason a reviewer would ever accept a draft that had just been deleted via an AfD discussion (much less one that had been deleted multiple times such as this one if my guess of which article this is about is correct). Also, I have never seen a need to see deleted versions. If I think it might meet G4, I just nominate it and an admin can make to decision but G4 should be very rare for drafts as one of the uses for AfC is to get an independent review of previously deleted articles. ] (]) 19:56, 20 December 2024 (UTC)

::::I don't see it often but I thought AFCH just said "The page xxxxx has been deleted Y time(s). View deletion log". That was the only part I was thinking could be a tad larger font as it gets lost compared to the big Accept/Decline/Comment buttons. If you then click on "View deletion log" (I think) it then shows the details but no auto show. SO actually if that was true rather than larger, it should just show the full details. However, I'm very tired I may just be remembering it wrong and can't find an example. ] (]) 20:49, 20 December 2024 (UTC)
Should I nominate this draft for speedy deletion? Earwig turns a '''''' similarity rate, but I fear this might be a false positive.<span id="LunaEclipse:1736769057670:Wikipedia_talkFTTCLNWikiProject_Articles_for_creation" class="FTTCmt"> —&nbsp;💽 ] 💽 🌹 ⚧ <sup>(''']''')</sup> 11:50, 13 January 2025 (UTC)</span>
:::::I think your memory is correct, Kylie. I don't think I've ever had any trouble noticing it but I'm sympathetic to the idea that it's easy to miss. @], were these AfC accepts both from the same reviewer? -- ] (]) 21:23, 20 December 2024 (UTC)

::::::Two different reviewers, both worthy wikipedians. The latest example, the one which I spoke about above is ], reviewed by ]. The other one was ], but I found out later the reviewer (]) was presented with ] and in the moment didn't see the previous deletions. IMHO, both reviewers made calls I might have made myself. ] (]) 21:53, 20 December 2024 (UTC)
:It is a false positive. You can see what's triggering the high percentage by clicking the "Compare" buttons to the left. It's detecting the award recipient list, which you can't really paraphrase. ] <i><sup style="display:inline-flex;rotate:7deg;">]</sup></i> 11:56, 13 January 2025 (UTC)
:::::::On my end, I didn't see anything related to deletion logs. I don't know if I missed it or if it just wasn't present, but I had no indication it had previously gone through anything since I hadn't noticed any logs. ''] Considerer:'' ''']''' (]) (]) 22:34, 20 December 2024 (UTC)
::Always, always, ''always'' do a check to see if the % actually means deletion is required. I declined a G12 earlier today where the ''second'' half of the draft was copied verbatim (and thus threw a 95% match) but after removal it didn't show any matches other than the random phrases like facility names. While the number is lower today than it used to, there are still some trigger-happy admins who will nuke anything G12 with a high % match without actually checking, and that does no favours to the user who submitted the draft if it's a "false positive" (at least as far as G12 goes). ] (]) 12:37, 13 January 2025 (UTC)
::::{{u|S0091}} is correct the text is big enough as I have just seen it again on ]. However, I do think the default state of the history should be expanded as it is important information that all reviewers should be aware of. ] (]) 19:30, 21 December 2024 (UTC)

:::::Now with fresh example, I agree the default should show the log info so you don't have to click on "view deletion log". It would actually be great to know it upfront but I'm not sure that's possible because the draft/sandbox title might change before a review which introduces various complications. However, it is aggravating to conduct an assessment then find out the deletion history after clicking Review. ] (]) 20:53, 21 December 2024 (UTC)
== Accepting when the mainspace title is create-protected (SALTed) ==
{{Tracked in|https://github.com/wikimedia-gadgets/afc-helper/issues/401}}
Eg, trying to accept ] gives:

:: Darn it, "]" is create-protected. You will need to request unprotection before accepting.

Can we have the script modified to cover these cases? It should prompt to request the deleting admin unprotect, or prompt to submit a request to unprotect at ], or here at ] where ] reliably does it?

Reviewers should not be sending the problem straight to DRV. DRV is for addressing deletion process problems or overturning a bad decision. —] (]) 02:55, 14 January 2025 (UTC)
:I am puzzled as to what ] says is wrong with the AFC script. The script did not say to go to ]. The script said to request unprotection. If SmokeyJoe is recommending that the script provide more detailed instructions, then that is a good idea, but the current instruction is not wrong. ] (]) 03:41, 14 January 2025 (UTC)
::The comment a reviewer posted on the draft “The author must take it to ] for review” was wrong. ] (]) 06:50, 14 January 2025 (UTC)
:::Not to get picky, but JoJo did say in their AFD close that any new drafts would need DRV to be accepted. Is this a proclamation they're allowed to make? I don't know, but that is why the reviewer said it. ] (]) 07:34, 14 January 2025 (UTC)
::::Good nitpick. I hadn’t seen that. I presumed it was a general belief that DRV is generally required to reverse SALTing, as we see from time to time at DRV.
::::] did say that in their close, in August 2017. I’m not wanting to try to solve this here, but the proclamation came from the closer, not the discussion, which is an issue. Also, time matters. I’ve seen elsewhere concerns about the huge number of protected pages, where most, but not all, never warranted permanent protection. I think JoJo’s proclamation should definitely be respected for six months, should probably be respected for two years, and after that I’m not sure. ] (]) 09:27, 14 January 2025 (UTC)
:::::Can't really argue with that; salting really is a slightly longer way of dealing with disruption, but I agree it shouldn't really ever be indef. ] (]) 09:35, 14 January 2025 (UTC)
::::::I am not personally sure myself, but my sense is that if a page keeps getting deleted at AfD, at some point folks need to challenge the AfD closes first (i.e DRV) before recreating yet again. That said, it's been eight years and I haven't worked in AfD for a long time. ] (]) 10:13, 14 January 2025 (UTC)
:If y'all want to pick which of those actions you want AFCH to do, I can make a ticket for it. We should focus on one action. So the workflow might be something like "Darn it, "Callum Reynolds" is create-protected. Do you want AFCH to file a request for unprotection at ]? ". Then the RFUP could be something like "I am an AFC reviewer and I would like to formally accept "Callum Reynolds" and move it to mainspace, but it is ]ed. I would like to request unprotection. Please ping me with the outcome so I remember to move the draft. Thanks." –] <small>(])</small> 06:35, 14 January 2025 (UTC)
::The simplest option I think is for AFCH to advise how to request unprotection.
::It might be good for AFCH to offer a post a canned request, to the protecting admin, or to RFUP, or to here at WT:AfC. ] (]) 06:48, 14 January 2025 (UTC)
:::Indeed. It would be fairly trivial to add something along the lines of "at RFUP or WT:AFC" after "unprotection". ] (]) 07:34, 14 January 2025 (UTC)
::::I with the "at RFUP or WT:AFC" addition. Let me know if anyone wants it adjusted. –] <small>(])</small> 09:37, 14 January 2025 (UTC)
:::::I suggest that it should say: "You will need to request unprotection from the protecting admin on their talk page or at ]." So +admin -WT:AfC. I don't think that WT:AfC should be recommended because RFUP ''should'' work, and if it isn't working, we should see why it isn't, instead of bypassing the problem by directing requests here. —] 15:06, 14 January 2025 (UTC)
::::::That's fair, I mainly was parroting Joe's suggestion since my advice here (when someone asks about a salted page) is to just ping me, well, here, and I'll take care of it. ] (]) 16:21, 14 January 2025 (UTC)
:::::::I updated the ticket to incorporate Alalch E's changes. –] <small>(])</small> 05:45, 15 January 2025 (UTC)

== Draft when article already exists ==

I just reviewed a draft that had been declined by two previous reviewers, both experienced editors, one of them an admin. On the one hand, I agreed that the draft, as submitted, did not establish ]. However, there was already an article on the subject. My question is why is it apparently easy for editors not to notice that there already is an article? The question was not whether the draft should be accepted, which is not possible if there is already an article. The questions were whether the draft should be declined as ''exists' or for notability, and whether the draft should be tagged for merging into the article. There is a notice in the yellow banner saying that there is already an article. Should it be made more prominent, or should reviewers be reminded to pay attention to it?

I had been planning not to name the draft, because I want a general response, not focused only on the specific draft, but then I realized that some reviewers will do their homework and look at my contribution history and see that it was ], and there already is an article on ], and the article, unlike the draft, does establish ]. So that is the specific. The fact that there already was an article was apparently missed by two reviewers. Do we need to make it easier for the reviewers?
] (]) 22:07, 15 January 2025 (UTC)
:Well, well. That sort of answers that. They are two different people. In that case, my only complaint is that it would have been helpful if the reviewers who declined the draft had noticed that disambiguation might be in order. ] (]) 22:17, 15 January 2025 (UTC)
::To answer the general question you asked (because the specifics just boil down to "reviewers need to take their damn time when they're reviewing"), it probably depends on how much more useful content there is in the draft. If it's an improvement, then a <code>merge</code> decline is probably more appropriate than the <code>exists</code> decline, which is really just more for saying "hey, don't waste your time on this, work on the article." Hell, we have the option to have multiple decline reasons, so just use both if it's borderline.
::I think the main reason we get duplicate submissions (based on a quick look through cats ] and ]) is disambiguation, whether a spelling difference or with parentheticals. I don't know how we can necessarily stop people from creating these pages, though. ] (]) 08:07, 16 January 2025 (UTC)

== Aram Mala Nuri, Requesting Review ==

Hello. It has been more than a month that I edited the last version and am waiting for response. If anyone could take a look and check it, it would be highly appreciated.
Here is the link of the draft:https://en.wikipedia.org/User:Zhewar_H._Ali/sandbox ] (]) 14:54, 17 January 2025 (UTC)
:{{u|Zhewar H. Ali}}, please be patient; drafts are not reviewed in any particular order but it will be seen in due time. ] (]) 15:05, 17 January 2025 (UTC)
::Thanks. The draft is again reviewed and edited with avoiding peacock terms, writing in a neutral tone and fixing inline citations. As for reliability of the sources I do not understand why they are not reliable. The sources are websites of organizations and presses, they may include no author names due to the lack of freedom of speech that reporters may receive threats on their lives if they show their names on the news and reports. Thanks for considering this. ] (]) 21:55, 18 January 2025 (UTC)
:::@], if you would like help understanding a review, the best places to ask are ] and ]. -- ] (]) 05:45, 19 January 2025 (UTC)

== BLP=yes, not living=yes ==
{{Tracked in|https://github.com/wikimedia-gadgets/afc-helper/issues/400|resolved}}
Hi, there is currently a ] running to change the ] that have living=yes to blp=yes. I just noticed that the AFC script if you tick that box. Can this please be changed to "blp=yes"? ] (]) 05:43, 18 January 2025 (UTC)
:Looks like it's in progress. ] (]) 07:32, 18 January 2025 (UTC)
:{{+1}} Also noticed this. ] (]) 14:15, 18 January 2025 (UTC)

== A doubt on ] drafts and species notability. ==

@] created a bunch of one-line one-sourced stub drafts and a bunch of mainspace stubs on species of ].

I declined the drafts as not meeting notability criteria, but after checking ], where every eukaryotes are presumed notable, I wonder if perhaps I should undo my declines? Even if they are one-line one-sourced stubs? <span style="background-color: RoyalBlue; border-radius: 1em; padding: 3px 3px 3px 3px;">''']''' <small>]</small></span> 19:50, 22 January 2025 (UTC)

:@], ] is for extant species, I just checked the last couple of declines and they were extinct so not covered. ] (]) 19:59, 22 January 2025 (UTC)
::Aha, skimmed over that part of the notability criteria. Thank you. <span style="background-color: RoyalBlue; border-radius: 1em; padding: 3px 3px 3px 3px;">''']''' <small>]</small></span> 20:00, 22 January 2025 (UTC)
:::It's pretty new. Only achieved guideline status within the last year. Easy to miss :) –] <small>(])</small> 03:08, 23 January 2025 (UTC)

== Promotions? ==

I've noticed the last promotion of probationary members was made all the way back in July 2024. Are these promotions carried out once in a while, like annually or something? Thanks. ] <small> (]) </small> 03:26, 23 January 2025 (UTC)
:I do biannual reviews at a minimum (makes for easier tracking of the non-probationary reviewers); I did start in December but unfortunately life got in the way as I was doing them so I only got a chance to remove some never-actives. It's on my list of things to do. ] (]) 08:45, 23 January 2025 (UTC)

Latest revision as of 10:52, 24 January 2025

Main pageTalk pageSubmissions
Category, Sorting, Feed
ShowcaseParticipants
Apply, By subject
Reviewing instructions
Help deskBacklog
drives

Welcome—discuss matters concerning this project!
AfC submissions
Random submission
2+ months
1,909 pending submissionsPurge to update
Shortcut


Skip to top Skip to bottom
          Other talk page banners
This project page does not require a rating on Misplaced Pages's content assessment scale.
It is of interest to the following WikiProjects:
WikiProject iconArticles for creation
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 projectWikiProject icon
To help centralize discussions and keep related topics together, Misplaced Pages talk:Articles for creation redirects here.
WikiProject Articles for creation was featured in a WikiProject Report in the Signpost on 24 December 2018.
Archiving icon
Archives
Articles for Creation (search)

1, 2, 3, 4, 5, 6, 7, 8, 9, 10
11, 12, 13, 14, 15, 16, 17, 18, 19, 20
21, 22, 23, 24, 25, 26, 27, 28, 29, 30
31, 32, 33, 34, 35, 36, 37, 38, 39, 40
41, 42, 43, 44, 45, 46, 47, 48, 49, 50
51, 52, 53, 54, 55, 56, 57, 58, 59

Reviewer help

Helper script

Participants

Old AFCH requests



This page has archives. Sections older than 20 days may be automatically archived by Lowercase sigmabot III when more than 6 sections are present.

AfC unreviewed draft statistics as of January 20, 2025


Disable AFCH if there is an ongoing AfD

The AFCH tool should be disabled if there is an ongoing AfD at the corresponding mainspace title, as with Draft:Raegan Revord and Misplaced Pages:Articles for deletion/Raegan Revord (2nd nomination), for example. GTrang (talk) 16:47, 31 December 2024 (UTC)

Why? A draft like that should be declined as exists anyway, so disabling AFCH would mean that we wouldn't be able to do that. Primefac (talk) 16:51, 31 December 2024 (UTC)
In fairness, that (decline as 'exists') is what GTrang did with this draft, but it was reverted as just extra administration for no reason (I think). Which then put the draft back in the pool. -- DoubleGrazing (talk) 16:57, 31 December 2024 (UTC)
I have undone that edit as the AFD is clearly trending towards the article being kept. Primefac (talk) 17:11, 31 December 2024 (UTC)
I went ahead and redirected the draft to the mainspace article, which is what I like to do in these situations to avoid duplication. I think editors should be encouraged to work on the mainspace article and not the draft, so that everyone is using their time efficiently. –Novem Linguae (talk) 22:57, 31 December 2024 (UTC)
I was reverted. NatGertler, can you please elaborate on how you plan to move a draft over an existing mainspace page? Did you perhaps mean that you plan to manually copy paste merge some pieces of the draft instead? In which case, the draft would be fine as a redirect, since the page history can easily be checked. –Novem Linguae (talk) 23:52, 31 December 2024 (UTC)
If you look at the AfD, there is reasonable support for (if the article survives AfD) deleting the version that is currently in mainspace and moving this draft one into mainspace at the same address. This version is in much better shape, and there is nothing substantial in the mainspace one that needs to be merged into this. If folks are to work on either of them, we want them working on this one, which is likely to be the surviving version in some form (whether it survives as a draft or in mainspace depends on the outcome of the AfD, but even at the most complicated take it will be merged into the mainspace one, so may as well have it here.) -- Nat Gertler (talk) 01:10, 1 January 2025 (UTC)
Got it. I think this should be de-duplicated at some point, but with your comment in mind, I suppose it's OK to wait until after the AFD is over. –Novem Linguae (talk) 01:26, 1 January 2025 (UTC)

Misplaced Pages:Declined AfC submissions resubmitted without any changes is live!

Per the outcome of this RfC, which is shown above, and a request filed at WP:BOTREQ by User:JJPMaster, the above page is now live and ready for reviewers to use, maintained by User:MolecularBot. It's actually caught 1 already in only the couple hours its been live, see Draft:M S Narasimha Murthy. :)

There's also a website I've made hosted on Toolforge to look up an article and see if it's resubmitted without changes, if that's more your thing.

For adding an item to the list, the requirement is that it has an AFC submission wizard edit, directly after an AFCH decline.

For removing an item from the list, the requirement is that it has a edit that is not done with AFCH or the AFC submission wizard (note: it's been very kindly suggested by Bunnypranav that it should maybe do some detecting to see if a edit is meaningful or not, any suggestions for when/when not a edit counts as meaningful are most welcome!)

Please don't hesitate to reach out to me if you have any feedback for this bot task, or would like anything changed about it. Thanks! :) MolecularPilot 06:25, 1 January 2025 (UTC)

Also btw an API is also available by sending a GET request to https://molecularbot2.toolforge.org/resubAPI.php?pageName=test, replacing test with the name of the page, excluding "Draft:"! :) MolecularPilot 06:26, 1 January 2025 (UTC)
Thanks for implementing the bot—on the new year nonetheless! Ca 13:47, 6 January 2025 (UTC)

Trying out using Microsoft Copilot to discuss notability of a particular topic

I'm not sure if people have tried this out or not. I searched AfC talk archives for "AI", "Gemini", "Copilot", and I saw that people have been talking about AI generated submissions, but I haven't seen any discussion on doing something like this.

So, anyway, I'll seek to share the dialog:

https://github.com/davidkitfriedman/general/blob/main/2025_01_02_dialog_with_Copilot_on_notability_of_GlobalProtect.md

I asked Copilot to argue against notability for GlobalPlatform, and then also to argue for notability.

Initially I just asked it what are some of the major consortia that Google is a part of.

Copilot responsed and then also prompted with, "Is there a specific area of Google's partnerships you're particularly interested in?".

And so I told it why I had asked the question initially, and it cited Misplaced Pages's policies, and then asked, "Do you have a specific consortium in mind that you're researching?"

I could mention that I did see this mentioned in Misplaced Pages:Artificial Intelligence, so perhaps editors don't feel that it's necessarily worth discussing with LLMs whether a particular topic meets notability or not.

When exploring AI techniques and systems, the community consensus is to prefer human decisions over machine-generated outcomes until the implications are better understood.

Jjjjjjjjjj (talk · contribs) 05:11, 3 January 2025 (UTC)

Meh... what people choose to do on their own time to not think for themselves is their own concern; if an LLM tells someone that a subject is notable, but the subject is not notable, we're no worse off than the Fiver writers that get paid to write shitty prose about non-notable grocery store owners. If the LLM tells the editor that a subject is notable, and they are, then all they've really done is waste their own time, since the subject would pass our criteria anyway. Primefac (talk) 07:05, 3 January 2025 (UTC)
LLMs do not think in the traditional human way because that's not what they're trained to do. Their job is to provide compelling output. The problem with that is that LLMs don't know what truth or factual accuracy is, i. e., they don't know if what they've just made up makes any sense. In a nutshell, discussing with an LLM is like talking to a parrot on steroids. --Johannes (Talk) (Contribs) (Articles) 08:20, 3 January 2025 (UTC)
I've seen several editors assuring us that their obviously LLM-generated draft has been painstakingly written to comply with all Misplaced Pages requirements for notability, verifiability, and other core policies yada yada... and then it turns out the said draft doesn't cite a single source. So if the editor hasn't the first clue about our requirements, then the LLM clearly won't impose one on them. -- DoubleGrazing (talk) 08:39, 3 January 2025 (UTC)
LLM and Misplaced Pages don't mix very well. In my opinion, in almost all cases, it's just a timesink. LLM is useful for certain non-Misplaced Pages things, but is not a great fit here. –Novem Linguae (talk) 17:38, 3 January 2025 (UTC)

African legislators

Just found out why we're seeing so many new drafts (mostly very short stubs) on legislators, esp. Nigerian ones, lately: https://meta.wikimedia.org/Event:African_Legislators_in_Red This runs until the end of the month, and one of the rules is that the articles must get into the main space by then, so expect to see some fast track requests at the help desk as the deadline approaches... -- DoubleGrazing (talk) 08:21, 4 January 2025 (UTC)

Ugh. People can wait. We don't expedite for contests. Primefac (talk) 13:53, 4 January 2025 (UTC)
hmm... I guess we do. Vanderwaalforces (intentionally not pinged) seems to be participating and reviewing drafts from this thing. Primefac (talk) 15:04, 4 January 2025 (UTC)
So long as it's individual reviewers making the offer to do it, seems fine to me. Not really different from someone, say, going through and reviewing all the OKA drafts (I've done this) or volunteering to help out with an editathon as a reviewer (I've done this, too). But I vote we ping Vanderwaalforces to each and every help desk request, if they arise. :P -- asilvering (talk) 16:15, 4 January 2025 (UTC)
Please do ping me if need arise! Vanderwaalforces (talk) 16:21, 4 January 2025 (UTC)
Oh, sure, I don't have any issue with them (or anyone else) making it a personal priority to help out, I'm just saying we-as-a-Project should not be expediting things. Primefac (talk) 16:23, 4 January 2025 (UTC)
I've been accepting a lot of these as inherently notable since I tend to camp out on the recently submitted feed but, yeah, I don't see why these endless stubs need to go through AfC..? qcne (talk) 15:34, 4 January 2025 (UTC)
Wait, they get money for this? I didn't think that was permitted? qcne (talk) 15:34, 4 January 2025 (UTC)
Based on what I could find (which was little more than this) it appears above-board, since they're not being paid to edit anything specific. Primefac (talk) 15:42, 4 January 2025 (UTC)
It's probably their way of having a check/balance for the stubs so that they don't have the issue that some other editathons have had where people spam utter garbage and maybe it gets reverted. Primefac (talk) 16:00, 4 January 2025 (UTC)
@Primefac Correct! Vanderwaalforces (talk) 16:23, 4 January 2025 (UTC)
@Qcne They actually need to go through AfC as a "damage control" both for English Misplaced Pages and the project itself. Also, these editors are mostly new, so yeah! Vanderwaalforces (talk) 16:23, 4 January 2025 (UTC)
Makes sense :) qcne (talk) 16:24, 4 January 2025 (UTC)
Most of them are easy to accept. I haven't come across too many issues (which is uncommon for contests with rewards), though some of the longer drafts do tend to lean on the promotional side. I've also found at least 3 copyvios stemming from this event from unrelated Copypatrol work, so be on the lookout for that I guess. C F A 17:55, 4 January 2025 (UTC)
@CFA Oh yes! I, in fact, disqualified one of the contestants for copyvio. I am especially not taking that lightly. By the way, I cannot thank you enough for keeping an eye on the article and tagging them with the WikiProject template, kudos! Vanderwaalforces (talk) 18:02, 4 January 2025 (UTC)

Draft nominated for MFD as not notable after decline

A draft BLP on a politician who does not meet political notability was declined, and then nominated for deletion by the reviewer who declined it. It was my understanding that AFC reviewers should know that drafts are not reviewed for notability or sanity. Either an AFC reviewer has been given access to the script who hasn't been adequately briefed as to how drafts are reviewed, including that they are only nominated for deletion in rare circumstances, or an editor who is not an AFC reviewer is reviewing drafts. Do the guidelines for reviewers need clarifying? We know that sometimes New Page reviewers mistakenly review new drafts with the same standards as they use to review new articles, but apparently some AFC reviewers also don't know when t not to send drafts to XFD. Robert McClenon (talk) 06:44, 5 January 2025 (UTC)

Or it could just be that the reviewer didn't know, and they could be gently told how to do it correctly. CaptainEek 07:38, 5 January 2025 (UTC)
I wouldn't necessarily call this a "hidden" rule or anything but I agree with Eek that "they didn't know" is probably the most likely scenario, and they should politely be a) informed, and b) asked to withdraw the MFD. Primefac (talk) 07:58, 5 January 2025 (UTC)
Context: Misplaced Pages:Miscellany for deletion/Draft:Bashir Muhammad Hussari Galadanchi. –Novem Linguae (talk) 11:10, 5 January 2025 (UTC)
I left the MFDer a message at their user talk about not MFDing drafts like this one in the future. They were receptive to the feedback. –Novem Linguae (talk) 11:51, 5 January 2025 (UTC)

Misplaced Pages:WikiProject Articles for creation/Submissions/List

is linked on the header, but I believe serves no purpose. This vaguely-named page doesn't have any "list" of submission by itself but links to two other lists. One of them, Misplaced Pages:AfC sorting, is already linked to by the header.

I propose it to be merged to its parent page /Submissions to reduce confusion and the clutter in the header. Only thing that really needs to be merged is the mention of Template:AfC statistics. Ca 14:00, 6 January 2025 (UTC)

Hasn't worked since at least 2022; you're just the second person to notice. Feel free to pull whatever you need from the history and plonk it elsewhere if that makes sense. Primefac (talk) 14:25, 7 January 2025 (UTC)

A little merging issue

Hello. Following a personal request for an AFC, I thought I would give it a try in spite of an article already existing as a redirect (never did). I over estimated my skills and need a little help :)

So the old article was a redirection (Lahcen Ahansal). I removed the redirection. Could not "Yes" the draft article under the right name (Draft:Lahcen Ahansal) becase of the already existing article. Thought I could approve it under a different spelling Lacen Ahansal and then merge their histories.

Ok, histories are not merging. What am I missing ? Anthere (talk) 14:09, 6 January 2025 (UTC)

I don't even understand, maybe because I am thinking about a lot of things. It does appear that Primefac has done something like that cleared the issue. Cheers!Safari Scribe 08:54, 7 January 2025 (UTC)
Anthere, there are a couple of other things you should have done. For anyone who isn't an admin, this is what should have been done
  • Request a {{db-afc-move}} on the redirect (this might have been declined given the old article's history, but then I -- as an admin -- would have probably just done a page swap)
  • Request a page swap at WP:RM/TR
For an admin, the options are:
  • Pageswap the draft and article
  • Move the old page (without redirect) to a disambiguated title
Copy/pasting a page to another location is not a good way to get a page to a specific title. Just to clear up SafariScribe's confusion, I just did a page swap on the two pages to put the new article at the correct title, while preserving the history of the old page.
As a minor note, Special:MergeHistory is only available to admins, which is why you couldn't use it. Primefac (talk) 13:52, 7 January 2025 (UTC) Struck, updated, and inserted: 14:07, 7 January 2025 (UTC)
I think Anthere is an admin. Is showing blue in my user highlighter script. –Novem Linguae (talk) 13:54, 7 January 2025 (UTC)
I was just going to say. And on multiple projects, it seems. -- DoubleGrazing (talk) 13:55, 7 January 2025 (UTC)
le sigh Forgive me for not having special admin-script glasses on.
A histmerge wasn't possible because there are (effectively) parallel histories; there was nothing that could be merged from the new page into the old page because of diffs from 2010 at the old page blocking the 2025 edits from the new. Primefac (talk) 14:04, 7 January 2025 (UTC)
This explains that... I felt vastly stupid :) Indeed, I could have swapped the two versions to have the new article history sitting at the right title. But I was trying hard to maintain both histories, which in fact was not really needed. Hmmm.
Situation is perfect now. Real author of current version is credited. All good. Thanks a lot for fixing. Anthere (talk) 20:27, 7 January 2025 (UTC)
Always happy to help, feel free to drop me a line any time you have histmerge questions, there are some who would say I'm an authority on the matter :-) Primefac (talk) 20:37, 7 January 2025 (UTC)

Non-English drafts

I've just declined yet another non-English draft (not the 1st one of the day, not even the 3rd, and that's just me!). In the Category:AfC submissions declined as not in English there are nearly 1,000 such declines. Would it be a good idea to put something in the wizard to warn authors that this is the English-language Misplaced Pages, and if they want to submit content in another language they should head to the relevant language version instead? It's mildly annoying to review these drafts, but I can imagine it's much more frustrating to put in all that effort, only to be told afterwards that it was all for nothing. -- DoubleGrazing (talk) 17:36, 7 January 2025 (UTC)

Probably, but if they're non-English-speaking then what are the realistic chances that they're going to read yet another banner telling them they shouldn't create pages in languages other than English? I'd rather avoid banner bloat if possible, and if the subject is notable it's a quick thing to decline as non-Eng and let them (or G13) sort it out. Primefac (talk) 18:16, 7 January 2025 (UTC)
In my experience they're not all (or even most?) "non-English-speaking"; many do subsequently communicate in English at the help desk and/or talk pages, and some even resubmit an English-translated draft. It's just that many seem genuinely surprised that the different language versions are in fact separate projects, and that submitting a Bulgarian (say) draft here doesn't help get it into the Bulgarian Misplaced Pages.
But yes, I take the point about banner bloat. Also, just because we warn them, doesn't mean they won't go against the warning regardless – after all, we get plenty of undisclosed COI/PAID submissions although the wizard clearly warns against these. -- DoubleGrazing (talk) 18:29, 7 January 2025 (UTC)
Fair enough. As usual, I'm not strictly opposed to adding something, just that my knee-jerk reaction is to wonder whether it's worth doing so... Primefac (talk) 18:31, 7 January 2025 (UTC)
I am wondering how feasible it may be to have a bot detect the language being used, and send a note to that editor in that language. BD2412 T 16:29, 11 January 2025 (UTC)
We have a number of non-English welcome templates, not sure a bot is needed, just a reviewer that doesn't mind taking an extra minute or two to leave one. Primefac (talk) 17:44, 11 January 2025 (UTC)
Often, when I decline a non English draft, I use machine translation to provide a message to the creating editor about it. I suppose it depends on how often it happens regrind a bot. I somehow doubt a bot is needed. 🇺🇦 Fiddle Faddle 🇺🇦 20:18, 11 January 2025 (UTC)
Agreed with Primefac that banner bloat would be bad, but we could have the AfC submit wizard identify the language and add a banner only if it's not English. Wikimedia now has its own translation service (mw:MinT), with includes a language identification API, so this can now be done without the privacy implications of using external services. – SD0001 (talk) 10:46, 24 January 2025 (UTC)
Tracked in github.com
Issue #8
Created an issue in the tracker. Please do use GitHub to log other ideas and suggestions for the AfC submit wizard, which otherwise get lost in the archives of this page. – SD0001 (talk) 10:52, 24 January 2025 (UTC)

Notified Jimbo instead of the user who submitted the draft

I accepted a draft created and submitted by an IP user, but the script actually notified Jimbo Wales instead of the IP user, I wonder what caused this? - Ratnahastin (talk) 09:11, 11 January 2025 (UTC)

@Ratnahastin: the submitting user changed the draft !ownership to Jimbo.
Or possibly Jimbo created it himself. In which case, you should go and warn him against editing logged-out. ;) DoubleGrazing (talk) 09:17, 11 January 2025 (UTC)

2026 United States Senate election in ...

Heads up: we've got five of these so far (see e.g. Draft:2026 United States Senate election in Arkansas) and I suspect more are coming. I dunno if it's WP:TOOSOON or not, but they look similar enough they can likely be accepted or declined as a group. Rusalkii (talk) 00:20, 12 January 2025 (UTC)

I'd decline all unless if there are secondary sources actually discussing the state-level senate elections. Ca 11:27, 12 January 2025 (UTC)

Draft:Clifford Prize

Should I nominate this draft for speedy deletion? Earwig turns a 93% similarity rate, but I fear this might be a false positive. — 💽 LunaEclipse 💽 🌹 ⚧ 11:50, 13 January 2025 (UTC)

It is a false positive. You can see what's triggering the high percentage by clicking the "Compare" buttons to the left. It's detecting the award recipient list, which you can't really paraphrase. Ca 11:56, 13 January 2025 (UTC)
Always, always, always do a check to see if the % actually means deletion is required. I declined a G12 earlier today where the second half of the draft was copied verbatim (and thus threw a 95% match) but after removal it didn't show any matches other than the random phrases like facility names. While the number is lower today than it used to, there are still some trigger-happy admins who will nuke anything G12 with a high % match without actually checking, and that does no favours to the user who submitted the draft if it's a "false positive" (at least as far as G12 goes). Primefac (talk) 12:37, 13 January 2025 (UTC)

Accepting when the mainspace title is create-protected (SALTed)

Tracked in github.com
Issue #401

Eg, trying to accept Draft:Callum_Reynolds gives:

Darn it, "Callum Reynolds" is create-protected. You will need to request unprotection before accepting.

Can we have the script modified to cover these cases? It should prompt to request the deleting admin unprotect, or prompt to submit a request to unprotect at WP:RFUP, or here at WT:AfC where User:Primefac reliably does it?

Reviewers should not be sending the problem straight to DRV. DRV is for addressing deletion process problems or overturning a bad decision. —SmokeyJoe (talk) 02:55, 14 January 2025 (UTC)

I am puzzled as to what User:SmokeyJoe says is wrong with the AFC script. The script did not say to go to DRV. The script said to request unprotection. If SmokeyJoe is recommending that the script provide more detailed instructions, then that is a good idea, but the current instruction is not wrong. Robert McClenon (talk) 03:41, 14 January 2025 (UTC)
The comment a reviewer posted on the draft “The author must take it to WP:DRV for review” was wrong. SmokeyJoe (talk) 06:50, 14 January 2025 (UTC)
Not to get picky, but JoJo did say in their AFD close that any new drafts would need DRV to be accepted. Is this a proclamation they're allowed to make? I don't know, but that is why the reviewer said it. Primefac (talk) 07:34, 14 January 2025 (UTC)
Good nitpick. I hadn’t seen that. I presumed it was a general belief that DRV is generally required to reverse SALTing, as we see from time to time at DRV.
User:Jo-Jo Eumerus did say that in their close, in August 2017. I’m not wanting to try to solve this here, but the proclamation came from the closer, not the discussion, which is an issue. Also, time matters. I’ve seen elsewhere concerns about the huge number of protected pages, where most, but not all, never warranted permanent protection. I think JoJo’s proclamation should definitely be respected for six months, should probably be respected for two years, and after that I’m not sure. SmokeyJoe (talk) 09:27, 14 January 2025 (UTC)
Can't really argue with that; salting really is a slightly longer way of dealing with disruption, but I agree it shouldn't really ever be indef. Primefac (talk) 09:35, 14 January 2025 (UTC)
I am not personally sure myself, but my sense is that if a page keeps getting deleted at AfD, at some point folks need to challenge the AfD closes first (i.e DRV) before recreating yet again. That said, it's been eight years and I haven't worked in AfD for a long time. Jo-Jo Eumerus (talk) 10:13, 14 January 2025 (UTC)
If y'all want to pick which of those actions you want AFCH to do, I can make a ticket for it. We should focus on one action. So the workflow might be something like "Darn it, "Callum Reynolds" is create-protected. Do you want AFCH to file a request for unprotection at WP:RFUP? ". Then the RFUP could be something like "I am an AFC reviewer and I would like to formally accept "Callum Reynolds" and move it to mainspace, but it is WP:SALTed. I would like to request unprotection. Please ping me with the outcome so I remember to move the draft. Thanks." –Novem Linguae (talk) 06:35, 14 January 2025 (UTC)
The simplest option I think is for AFCH to advise how to request unprotection.
It might be good for AFCH to offer a post a canned request, to the protecting admin, or to RFUP, or to here at WT:AfC. SmokeyJoe (talk) 06:48, 14 January 2025 (UTC)
Indeed. It would be fairly trivial to add something along the lines of "at RFUP or WT:AFC" after "unprotection". Primefac (talk) 07:34, 14 January 2025 (UTC)
I made a ticket with the "at RFUP or WT:AFC" addition. Let me know if anyone wants it adjusted. –Novem Linguae (talk) 09:37, 14 January 2025 (UTC)
I suggest that it should say: "You will need to request unprotection from the protecting admin on their talk page or at WP:RFUP." So +admin -WT:AfC. I don't think that WT:AfC should be recommended because RFUP should work, and if it isn't working, we should see why it isn't, instead of bypassing the problem by directing requests here. —Alalch E. 15:06, 14 January 2025 (UTC)
That's fair, I mainly was parroting Joe's suggestion since my advice here (when someone asks about a salted page) is to just ping me, well, here, and I'll take care of it. Primefac (talk) 16:21, 14 January 2025 (UTC)
I updated the ticket to incorporate Alalch E's changes. –Novem Linguae (talk) 05:45, 15 January 2025 (UTC)

Draft when article already exists

I just reviewed a draft that had been declined by two previous reviewers, both experienced editors, one of them an admin. On the one hand, I agreed that the draft, as submitted, did not establish biographical notability. However, there was already an article on the subject. My question is why is it apparently easy for editors not to notice that there already is an article? The question was not whether the draft should be accepted, which is not possible if there is already an article. The questions were whether the draft should be declined as exists' or for notability, and whether the draft should be tagged for merging into the article. There is a notice in the yellow banner saying that there is already an article. Should it be made more prominent, or should reviewers be reminded to pay attention to it?

I had been planning not to name the draft, because I want a general response, not focused only on the specific draft, but then I realized that some reviewers will do their homework and look at my contribution history and see that it was Draft:Caitlin McCarthy, and there already is an article on Caitlin McCarthy, and the article, unlike the draft, does establish acting notability. So that is the specific. The fact that there already was an article was apparently missed by two reviewers. Do we need to make it easier for the reviewers? Robert McClenon (talk) 22:07, 15 January 2025 (UTC)

Well, well. That sort of answers that. They are two different people. In that case, my only complaint is that it would have been helpful if the reviewers who declined the draft had noticed that disambiguation might be in order. Robert McClenon (talk) 22:17, 15 January 2025 (UTC)
To answer the general question you asked (because the specifics just boil down to "reviewers need to take their damn time when they're reviewing"), it probably depends on how much more useful content there is in the draft. If it's an improvement, then a merge decline is probably more appropriate than the exists decline, which is really just more for saying "hey, don't waste your time on this, work on the article." Hell, we have the option to have multiple decline reasons, so just use both if it's borderline.
I think the main reason we get duplicate submissions (based on a quick look through cats this and that) is disambiguation, whether a spelling difference or with parentheticals. I don't know how we can necessarily stop people from creating these pages, though. Primefac (talk) 08:07, 16 January 2025 (UTC)

Aram Mala Nuri, Requesting Review

Hello. It has been more than a month that I edited the last version and am waiting for response. If anyone could take a look and check it, it would be highly appreciated. Here is the link of the draft:https://en.wikipedia.org/User:Zhewar_H._Ali/sandbox Zhewar H. Ali (talk) 14:54, 17 January 2025 (UTC)

Zhewar H. Ali, please be patient; drafts are not reviewed in any particular order but it will be seen in due time. Primefac (talk) 15:05, 17 January 2025 (UTC)
Thanks. The draft is again reviewed and edited with avoiding peacock terms, writing in a neutral tone and fixing inline citations. As for reliability of the sources I do not understand why they are not reliable. The sources are websites of organizations and presses, they may include no author names due to the lack of freedom of speech that reporters may receive threats on their lives if they show their names on the news and reports. Thanks for considering this. Zhewar H. Ali (talk) 21:55, 18 January 2025 (UTC)
@Zhewar H. Ali, if you would like help understanding a review, the best places to ask are WP:AFCHELP and WP:TEA. -- asilvering (talk) 05:45, 19 January 2025 (UTC)

BLP=yes, not living=yes

Tracked in github.com
Issue #400
Resolved

Hi, there is currently a bot running to change the ~300000 articles that have living=yes to blp=yes. I just noticed that the AFC script creates living=yes if you tick that box. Can this please be changed to "blp=yes"? The-Pope (talk) 05:43, 18 January 2025 (UTC)

Looks like it's in progress. Primefac (talk) 07:32, 18 January 2025 (UTC)
+1 Also noticed this. CNC (talk) 14:15, 18 January 2025 (UTC)

A doubt on Jujubinus drafts and species notability.

@TrueMoriarty created a bunch of one-line one-sourced stub drafts and a bunch of mainspace stubs on species of Jujubinus.

I declined the drafts as not meeting notability criteria, but after checking WP:NSPECIES, where every eukaryotes are presumed notable, I wonder if perhaps I should undo my declines? Even if they are one-line one-sourced stubs? qcne (talk) 19:50, 22 January 2025 (UTC)

@Qcne, Misplaced Pages:Notability (species) is for extant species, I just checked the last couple of declines and they were extinct so not covered. KylieTastic (talk) 19:59, 22 January 2025 (UTC)
Aha, skimmed over that part of the notability criteria. Thank you. qcne (talk) 20:00, 22 January 2025 (UTC)
It's pretty new. Only achieved guideline status within the last year. Easy to miss :) –Novem Linguae (talk) 03:08, 23 January 2025 (UTC)

Promotions?

I've noticed the last promotion of probationary members was made all the way back in July 2024. Are these promotions carried out once in a while, like annually or something? Thanks. ABG (Talk/Report any mistakes here) 03:26, 23 January 2025 (UTC)

I do biannual reviews at a minimum (makes for easier tracking of the non-probationary reviewers); I did start in December but unfortunately life got in the way as I was doing them so I only got a chance to remove some never-actives. It's on my list of things to do. Primefac (talk) 08:45, 23 January 2025 (UTC)
Category:
Misplaced Pages talk:WikiProject Articles for creation: Difference between revisions Add topic