User talk:Rsjaffe/Archives/2023/March

Guild of Copy Editors March 2023 Newsletter

Guild of Copy Editors March 2023 Newsletter Hello and welcome to the March 2023 newsletter, a quarterly digest of Guild activities since December and our Annual Report for 2022. Don't forget you can unsubscribe at any time; see below. We extend a warm welcome to all of our new members, including those who have signed up for our current March Backlog Elimination Drive. We wish you all happy copy-editing. Election results: In our December 2022 coordinator election, Reidgreg and Tenryuu stepped down as coordinators; we thank them for their service. Incumbents Baffle gab1978, Dhtwiki, Miniapolis and Zippybonzo were returned as coordinators until 1 July. For the second time, no lead coordinator was chosen. Nominations for our mid-year Election of Coordinators open on 1 June (UTC). Drive: 21 editors signed up for our January Backlog Elimination Drive, 14 of whom claimed at least one copy-edit. Between them, they copy-edited 170 articles totaling 389,737 words. Barnstars awarded are here. Blitz: Our February Copy Editing Blitz focused on October and November 2022 requests, and the March and April 2022 backlogs. Of the 14 editors who signed up, nine claimed at least one copy-edit; and between them, they copy-edited 39,150 words in 22 articles. Barnstars awarded are here. Drive: Sign up now for our month-long March Backlog Elimination Drive. Barnstars awarded will be posted here after the drive closes. Progress report: As of 12:08, 19 March 2023 (UTC), GOCE copyeditors have processed 73 requests since 1 January 2023, all but five of them from 2022, and the backlog stands at 1,872 articles. Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Baffle gab1978, Dhtwiki, Miniapolis and Zippybonzo. To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

ANI deleted discussion

Hello, I noticed that you had deleted the discussion I had started in ANI, but I had requested earlier in the day for it not to be archived and I think it may have been overlooked by mistake.

Is there any way to have it opened back up so that I can address the users I had mentioned in the request above? I also think I owe the original user an apology, and wanted to try to do that in the ANI post, if possible. Thank you!

Awshort (talk) 04:00, 21 March 2023 (UTC)

I don't think I deleted anything there. I certainly wasn't trying to. Check the page history to see who deleted or archived it. — rsjaffe 🗣️ 04:07, 21 March 2023 (UTC)

Please don't warn experienced users about their Drafts

I noticed your comment (diff) regarding foreign-language text in Draft:Rubricaire. May I ask you if there is a feed or category or batch report or something which listed this, or can you tell me how you found this draft? I believe the process/report/category concerned may have an error that needs to be corrected, as this Draft never should have been listed as needing attention.

With limited exceptions for content that is *never* permitted anywhere on Wikipedia (WP:LIBEL, WP:COPYVIO, etc.), please do not warn a user on their Talk page about problems in unsubmitted Drafts, including no references, bad references, empty sections, misleading information, inaccurate information, essay-like material, bad formatting, inscrutable text, machine translation, bad translation, wrong language, incorrect spelling, grammar, or syntax, MOS violations, or any of that stuff. That's what a draft is for, so you can develop the article without worrying about content that does not (yet) meet Wikipedia policies and guideline standards. Friendly comments at Draft talk:ArticleName with ideas of how to improve the draft are always welcome. In the particular case linked above, 15-year editor Elinruby with dozens of created articles (including many translations) to their credit hardly needs to be reminded that this is English Wikipedia, and telling him to translate foreign text comes off as patronizing, or a bit insulting.

Please do let me know how you ended up at that draft, and I will follow up and try to ensure that Drafts are not mistagged for this type of attention. I appreciate your looking out for the quality of Drafts, and I'm aware there's a backlog, and your work evaluating Drafts is very important, so carry on, and thanks for all your efforts! Cheers, Mathglot (talk) 22:23, 21 March 2023 (UTC)

oh he's an ok guy, he did apologize. But yes this was some sort of patrol, probably NPP. Not particularly mad at him. It was just an unfortunate algorithm, which to their credit NPP has adjusted, just not enough. Basically anything over an hour is the new parameter. The other problem is that you get this message if the article contains any foreign language at all, even if it's small as this was. It could use some fine-tuning, as a technical note. Elinruby (talk) 23:10, 21 March 2023 (UTC)

Yeah, I did make a mistake by templating it—I thought it had been mistakenly stopped mid-translation and wanted to bring it to their attention. Should have just left a note. No algorithm involved, I’ve recently been looking for new evidence of LLM/AI misuse, and just ran across that page. In terms of actions, have been primarily identifying LLM pages and using a template I helped develop that explains the issue with LLMs, as I’ve seen lots of naive use that started leaking into article space and wanted to help people understand the problem upstream of that, as that would stop them from wasting their time with LLMs, which are woefully unsuited for anyone other than a sophisticated user. I’ve markedly reduced my activity in this sphere, as a policy is closer to proposal stage and people in general are starting to hear better-balanced reporting about the benefits and drawbacks of LLMs, as opposed to the unalloyed hype we initially were being fed. — rsjaffe 🗣️ 04:21, 22 March 2023 (UTC)

Chatbot

If so, iy's not doing a good job at all. -- Deepfriedokra (talk) 14:39, 31 March 2023 (UTC)