User talk:ClueBot Commons

The current status of ClueBot NG is: Running
Praise should go on the praise page. Barnstars and other awards should go on the awards page.
Use the "new section" button at the top of this page to add a new section. Use the [edit] link above each section to edit that section.
This page is automatically archived by ClueBot III.
The HomoBots' owner or someone else who knows the answer to your question will reply on this page.

Beware! This user's talk page is monitored by talk page watchers. Some of them even talk back.

Messed up archiving

Somehow I messed up the archiving setup at User:Ww2censor/SuggestBot. I wanted to archive the SuggestBot's monthly posts into managable proportions but the first time it ran your bot moved all 40 discussions into the 1st archive page and due to the size took a long time. I mostly reverted it but it di so again. Today it has moved all the newer posts again even though I wanted to keep 2 posts on the page after each archive run. Can you help me figure this out? Can we start over from scratch from this edit? I can always copy paste in the April and May update once it is working correctly. TIA ww2censor (talk) 09:08, 23 May 2014 (UTC)

Based on your statement that you want the current threads to be separated into multiple different archives, I am changing your configuration from ClueBot III (CB3) to lowercase sigmabot III (lcSB3). CB3 will always archive everything it is supposed to archive any single time it is run into one archive file. While this is fine if CB3 is continuously running on a page, it means that a backlog that exists at the time you set up archiving will get dumped into one and only one archive. You could get around this by manually changing the archive time after each run to progressively archive portions of the page, but that is inconvenient and takes greater attention oer time which setting it up. It is much easier in this case to use lcSB3 which will take the backlog and put it into multiple different archive pages. This will take a bit. I will post when done. — Makyen (talk) 16:36, 23 May 2014 (UTC)

 Done All of the edits I expect to make to correct the situation are complete. I have reverted all content back to the User:Ww2censor/SuggestBot page and placed a lcSB3 config on the page. There were some things in your CB3 config which were wrong, so I corrected them to what I think you wanted based on your comments above and common usage. The most significant was the archive location which was invalid and CB3 had used its default archive page location combined with the |format= %%i you had. You also had |minarchthreads=2 in what I believe was an attempt to keep two threads on the page when archiving happened. This parameter actually told CB3 not to archive unless it was able to archive at least 2 threads. The parameter you actually wanted was |minkeepthreads=2} which would have kept two threads on the page. The configuration is now as I believe you desire it.

Yet to happen is the deletion of the pages created by CB3. I have tagged them for speedy deletion with {{db-g6}} as they were created in error. I also created an archive index page out of habit. Belatedly, I noticed that your CB3 config explicitly configured no indexing. I have also tagged for deletion the index page I erroneously created and removed both the archive indexing config from User:Ww2censor/SuggestBot and the link which I had included in the archive box. — Makyen (talk) 17:56, 23 May 2014 (UTC)

Looks good so far and we shall see when the bot runs on it again. However, I didn't actually want each thread to be a separate archive but to be managebale chunks of multiplpe threads, such as 100K max. Is that possible or a suitable size? Thanks for the speedy response. ww2censor (talk) 19:18, 23 May 2014 (UTC)

It appears I did not communicate as I intended. As it is, lcSB3 will create archive pages which are each approximately 150k in length containing the number of threads which are needed to get to that length. While it will do so in a single archive task, it will create as many archive pages as are needed to archive the threads it is supposed to – leaving at least 2 on the page (|minthreadsleft=2) – while keeping each archive page to about 150k. The length is approximate because none of the bots break a single thread into chunks. The only reason I set it to 150k is that 150k was the length which I found in |maxarchsize=150000 within the CB3 config when I started making changes. When I set up archiving, I usually use a 100k length, just because. I highly recommend not over 230k because strange things can happen when a page is > 256kiB and archives are not guaranteed to be a specific length.

You can set the archive target size to whatever you desire. It is set in the |maxarchivesize= parameter.

Just to confirm: All pages I had marked for deletion have been deleted.

I should have stated this in my prior posting: As is my normal practice when helping like this, I will watch the page at least through the first archiving task that lcSB3 runs just to be sure that there are no problems. — Makyen (talk) 22:20, 23 May 2014 (UTC)

Brilliant, I really appreciate the help. Thanks. ww2censor (talk) 10:15, 24 May 2014 (UTC)

User warning

I'd like to ask that the bot recognizes blanked warnings and proceeds to the next one on the list, because when editors blank the warnings and continue to vandalize, cluebot gives them a lv1 warning all over again. --Lixxx235 (talk) 05:29, 26 May 2014 (UTC)

@Lixxx235: I think it was deliberately designed this way so users wouldn't receive escalating warnings if they did what the lvl 1 warning notice instructed them to do - remove the notice, report the false positive, and then make the edit again. Removing the warning is to prevent the bot from eventually reporting innocent users to WP:AIV. Once a false pos is reported, it must first be reviewed by a human before it is added to the corpus, so until that happens the bot will still revert an edit with the same text. However, Huggle sees through this and escalates even when warnings are blanked, and even if CBNG or another user adds a level 1 warning after a level 3 warning was issued. --k6ka (talk | contribs) 20:06, 26 May 2014 (UTC)

A barnstar for you!

	The Anti-Vandalism Barnstar
	;) Iiboharz (talk) 12:39, 26 May 2014 (UTC)

Lies

Your a liar, I didn't vandalise anything. You suck — Preceding unsigned comment added by 88.105.57.154 (talk) 23:08, 27 May 2014 (UTC)

All right, let's suppose your edits to Yorkshire dialect were a good-faith effort to add a little humour into the article. An edit made in genuine good faith should not be considered vandalism – yet we would still ask you, please, to not make joke edits. Readers looking for accurate information will not find them amusing. You might have guessed this when your edit was reverted by a human editor the first time, before Cluebot NG even got involved. Also, please refrain from using insults on a talk page. (I'm not sure why you would bother insulting a bot, anyway.) Thanks. – Wdchk (talk) 00:52, 28 May 2014 (UTC)

Jhené Aiko

I got a warning for editing the page for Jhené Aiko. I was trying to put the pronunciation of Aiko (ah-ee-ko) because for some crazy reason people do not understand how to pronounce it even after she has said it a million times. Unsigned comment by AceyBae

It looks like you bumped into a false positive. Did you know reporting these helps ClueBot to not make the same mistake again? So, why not report a false positive at the Report Interface – it's really easy to do! Thank you. Bilorv (talk) 14:15, 29 May 2014 (UTC)

Hi

This is for you

Nya Long (talk) 16:29, 29 May 2014 (UTC)

Doppelganger accounts for Bots

Hey, i think that Cluebot and the others should have Doppelganger accounts, especially with this incident-User:ClueBot GN ynow? --Coo coo pigeon (talk) 05:48, 30 May 2014 (UTC)

A barnstar for you!

	The Anti-Vandalism Barnstar
	:-) ♥ Solarra ♥ ♪ 話 ♪ ߷ ♀ 投稿 ♀ 06:49, 30 May 2014 (UTC)