This is an archive of past discussions with User:ClueBot Commons. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
@Shiftchange: ClueBot III's archive template can produce its own archive box. I removed the other one and used the CBIII one instead, and it appears to be working now. --k6ka (talk | contribs) 12:56, 31 May 2014 (UTC)
@Shiftchange:, @K6ka: The root issue was that the archiving page name in |archiveprefix= was not changed when the configuration was copied from one page to the next. The archiving configuration templates require hard coded archive prefix names. For ClueBot III (CB3), if the name is wrong CB3 will use its default prefix name. Unfortunately, the default is wrong for numbered archive pages. When pasting the CB3 archive template into a new page which is going to use numbered archive pages I recommend using:
|archiveprefix={{subst:FULLPAGENAME}}/Archive
That will result in the current page name being substituted in the correct location.
I have done the following to correct the various issues and complete installation:
Returned the archive box to the one previously used.
Created the archive index page with contents to transclude the index generated by CB3.
Changed the archive box to include a link to the index page.
Changed the CB3 generated index pages (2x) to point to the moved archive page. These will be regenerated by CB3 the next time it runs, but I wanted no links to the erroneous page so that:
Tagged the erroneously created page for deletion via {{db-g6}}.
I have also
Reorganized the order of talk page headers so that the archive box and TOC line up (also added a style to the archive box so that it is actually lined up vertically with the TOC instead of being off by a few pixels).
Moved the bare text acting as a notice on the page into a {{Notice}} template. I retained the spacing that was being used, but I recommend removing the extra spaces in the header. Retain them if you are really having a significant problem with people putting new sections at the top of the page.
Added a link in the archive box to the created archive index
Lined up TOC and archive box vertically: Forced a TOC, adjusted vertical spacing of archive box, and forced the TOC and archive box to complete prior to beginning page sections.
This should be done at this point with the exception that the erroneous page still needs to complete the deletion process. — Makyen (talk) 15:32, 31 May 2014 (UTC)
Highest edit?
I'm meaning in terms of the vandal score. I've seen a couple .97's, but has there ever been a 1.0 or a .999 or something like that? Kind of curious. Tutelary (talk) 23:32, 31 May 2014 (UTC)
I'm not too slick with ClueBot knowledge. I have an archive template on my talk page, which was set for 720 hours (30 days), however Clue hasn't archived in a couple of months. I've changed the number to 721 with the hope that ClueBot will notice it. Anybody have any suggestions? Sorry if it's a n00b style question. Cyphoidbomb (talk) 17:00, 1 June 2014 (UTC)
You don't need to report the false positive on the talk page. I see you reported it at the correct location, so that's good. --k6ka (talk | contribs) 17:17, 3 June 2014 (UTC)
I have a hypothetical question for those whom it may concern. If I move a talk page which is archived by ClueBot III, (along with existing archives, to an appropriate location):
Will the bot continue to archive the page?
Will the index page be updated to refer to the new page and archive subpages, or will a "copy" be generated?
Will the bot pick up on existing archives or try to generate new ones?
(talk page stalker) The following is from memory of a variety of clean-ups and extrapolating, off-the-cuff, from observed behavior. Thus, it may be inaccurate.
The archive page location is hard-coded in the configuration template. Except under specially configured circumstances, the archive location must be a subpage of the current page. The bot does not take into account redirects when testing for this. Without editing the archive configuration template the archive location will point to the old page location. The archive location will thus be considered invalid and the default archive location will be used. While it is possible that the default location is the desired location (more likely if archives are organized by date, not numbered), it is probable that the default location will not be desired. This may result in the need for considerable cleanup/reorganization if the issue is not noticed for a considerable time. So, yes the bot will continue to archive the page, but it is likely to be erroneous.
The indexes appear to be completely re-generated each time. Given that the newly generated index is identical if the source pages have not changed and how the MediaWiki software works, it appears, from a viewer's point of view, that CB3 only makes changes. However, erroneously using the default location can lead to a variety of undesired issues (one example of an erroneous detailed index). The old index will be orphaned and no longer linked. I have not checked on its eventual disposition.
Assuming that the default location is not the desired/correct location, new archive pages will be generated for any content newly archived from the talk page.
If the existing archive pages are moved to the same relative locations along with the main talk page and the ClueBot III configuration template |archiveprefix= is edited to reflect the new page location instead of the old page location, then archiving will be performed normally with all existing archives being recognized properly.— Makyen (talk) 22:19, 11 June 2014 (UTC)
@BrandonKF:, you have reverted some vandalism to the last version by ClueBot NG. What you did was good. Thank you for catching and taking care of that vandalism. Another time, it is not necessary to inform the user responsible for the version to which you are reverting. In general, the user will have the page on their watchlist if they desire to know about changes to the page.
You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.
The article will be discussed at Wikipedia:Articles for deletion/16874 Kurtwahl until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. Launchballer22:29, 22 June 2014 (UTC)
This bot is really dumb sometimes
This bot recently reverted my change on the Anna Paquin article, where I reverted some vandalism. Somehow, this bot was too stupid to realize that an edit adding thousands of nonsense characters was vandalism, but my edit reverting it wasn't. Bots like this are the reason I don't contribute to Wikipedia anymore. The last few times I've tried to make an edit (mostly to revert vandalism or fix grammar), it's been automatically reverted by bots. It seems that Wikipedia is biased against new contributors, especially those of us who don't want to bother making an account. You guys should try to reduce the false positive rate. By the way, I'm probably never going to bother making edits ever again. What's the point, when most of them get (falsely) reverted anyway? — Preceding unsigned comment added by 162.211.217.252 (talk) 05:42, 20 June 2014 (UTC)
Bots are not perfect. If the bot has made a mistake, report it here so the error can be investigated. The bot's false positive rate is at 0.1% (that's extremely low), and the bot developers are sorry for any errors the bot makes. The bot, however, is very complex and it's bound to make mistakes.
We're sorry to hear that you are leaving Wikipedia. We understand that, eventually, an editor may need to leave for one reason or another. We hope that you'll come back, because we could really use the help! Also, don't be angry if a bot mistakenly reverts your edit. The bot is bound to make mistakes, but in the end rest assured that a human is the barrier between a broken bot and you. So don't worry about it. --k6ka (talk | contribs) 13:22, 23 June 2014 (UTC)