User talk:ClueBot Commons/Archives/2018/March

ClueBot continues to be wrong 100% of the time
I have undone this edit by ClueBot and reported it via the interface provided for ClueBot's false positives.

ClueBot should be programmed to stay away from mathematical notation. I've never seen an edit by ClueBot to an article I've edited when ClueBot's edit was not garbage. Michael Hardy (talk) 21:47, 27 February 2018 (UTC)
 * Thanks for reporting this. ClueBot NG does sometimes have issues with LaTeX logo.svg notation.  This is something that we hope to address.  But ClueBot NG uses an Artificial Neural Network to learn and score edits, and a decent number of edits it has seen to LaTeX logo.svg notation have been vandalism.  In the mean time, ClueBot NG honors nobots, and that can be used to ward off articles where the bot has issues while the underlying issues are corrected.
 * That being said, your edit summary for the revert and the section header of this section are misleading. ClueBot NG's false positive rate is nowhere near 100%, even if restricted to mathematical notation.  And WP:VAND defines vandalism to be editing deliberately intended to obstruct or defeat the project's purpose.  I can very assuredly say that ClueBot NG's reverts are not deliberately intended to obstruct or defeat the project's purpose.  -- Cobi(t&#124;c&#124;b) 21:42, 28 February 2018 (UTC)
 * I've added a nobots template to that article. ClueBot should stay from it.  I should point out that ClueBot's false positive rate on the entire project is extremely low, and that you are unfortunately watching articles ClueBot happens to struggle more on.  Hell, I would have thought that edit was vandalism, as I'm not very familiar with Latex notation.— CYBERPOWER  (Around ) 02:10, 1 March 2018 (UTC)

That is a very harshly written message that seems to have been scribbled down out of frustration. "100%" is a blatantly obviously incorrect exaggeration and it makes CBNG look like a vandal bot bent on destroying Wikipedia, which undoubtedly insults the people that have spent hours working on the bot as well as the people who do appreciate what the bot has done. I am even more surprised that this comes from an administrator. — k6ka  🍁 ( Talk ·  Contributions ) 11:29, 1 March 2018 (UTC)
 * Hours? Try months, with constant training.— CYBERPOWER  ( Message ) 04:32, 2 March 2018 (UTC)

reCAPTCHA v1 will break after March 31
When I visited the report interface to report a mistake, I got this message in the reCAPTCHA box:


 * V1 shutdown on 2018-03-31. Direct site owners to g.co/recaptcha/upgrade

The report interface should be upgraded to the latest version of reCAPTCHA before the end of this month so it doesn't stop working.

StephenWade (talk) 14:11, 8 March 2018 (UTC)

Proper use of the ArchiveThis Template
Hello, in this edit, User:John of Reading used the edit summary to advance the claim that "Add archiveprefix - although that's the default value, the indexer doesn't work properly without it." This seems to contradict User:ClueBot III/ArchiveThis's If you do not set this argument, or if you set it to something invalid, then the default value will be used. Can you clarify which is the desired template configuration if one simply wants to use the default? Can you also clarify what ClueBot III does to handle archiving across page moves if the archiveprefix is overlooked during the move? Is there any way that the template or its doc page can be changed to make using archiveprefix easier in the overwhelming number of cases where people just want the default archive location? Thanks. -- DanielPenfield (talk) 18:24, 8 March 2018 (UTC)
 * archiveprefix is currently required for the archivebox to work correctly. If you read the next sentence "However, not setting this parameter correctly can have some strange results," you'll see that it is properly required.  User:ClueBot III/ArchiveThis is the desired template configuration if you just want some defaults.  Or you can use .  The template parameters will have to be updated if the page is moved.  -- Cobi(t&#124;c&#124;b) 20:34, 9 March 2018 (UTC)

ClueBot III and the spam blacklist
I've noticed that ClueBot III has occasionally caused spam blacklist hits when attempting to archive discussions (see Special:Log/spamblacklist/ClueBot III (you have to be logged in to view it)). — MRD2014 Talk 21:18, 9 March 2018 (UTC)

reCAPTCHA v1 will break after March 31
When I visited the report interface to report a mistake, I got this message in the reCAPTCHA box:
 * V1 shutdown on 2018-03-31. Direct site owners to g.co/recaptcha/upgrade

The report interface should be upgraded to the latest version of reCAPTCHA before the end of this month so it doesn't stop working. StephenWade (talk) 14:11, 8 March 2018 (UTC)

Photography workshop
- why Feb? Is there something wrong with the Cluebot configuration at Graphics Lab/Photography workshop? I can't see any reference to, or relation to February in what was archived at that diff. Thanks for any pointers you can offer. I just shifted about 30k of stuff between Jan/Feb/Mar archives prior to this Cluebot edit thinking it must just be human error that had caused the wrong archives to be used, but now Cluebot subsequently does this and I am confused. I may well be missing something obvious, but it'd be nice if we can fix it.
 * Also, while I'm here, can we replace " in that config with " or something similar, to avoid needing to/forgetting to update it - or will that not get properly evaluated? I strongly suspect this won't work, because the outer {{'s are passed without expansion, so {{tq|1=" {{CURRENTYEAR}} "}} will be too, but is there a workaround? -- Begoon 11:54, 27 March 2018 (UTC)
 * The Graphics Labs use manual archive navigators, so I didn’t see the benifit to the automatic year-changing as someone has to set that page up anyway. Many of the “more complex” autoarchived pages also need yearly intervention. Also, if someone makes changes to the configuration, please copy it to the other GLs. Thanks! —AntiCompositeNumber (talk) 12:19, 27 March 2018 (UTC)
 * Well I guess the "benefit" would be that the hypothetical, helpful person who may just create the new header page because the archive page seems "wrong" (or for any other reason) would not also have to remember (or even know) that another configuration needed changing somewhere else also... Guess who forgot to change that when creating Wikipedia:Graphics Lab/Photography workshop/Archive/2018...{{p}} ? Anyway, my main concern is to find out why it is archiving to the wrong page, this was just an additional wish/question. -- Begoon 13:09, 27 March 2018 (UTC)

Task request
Per this discussion, can you implement a bot task to detect and correct when Template:User:ClueBot III/ArchiveThis's archiveprefix was omitted by the editor or when archiveprefix includes one or more mw:Help:Magic_words? This probably needs to be an ongoing task. Thanks. -- DanielPenfield (talk) 05:25, 29 March 2018 (UTC)