User talk:ClueBot Commons/Archives/2025/August

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.

@ClueBot Commons Hi friends, can you tell me how to delete the table format because I saw that the Malay Wikipedia has a bit of the same format but the English one is different. I was wondering if I could change the table a bit and delete it? BASIKAL 122 (talk) 04:42, 31 July 2025 (UTC)

ClueBot is a bot, an automated process, to either remove vandalism or archive talk page. We cannot help you with that 94.15.150.204 (talk) 94.15.150.204 (talk) 13:50, 31 July 2025 (UTC)

I have enabled highlighting of bot edits in my watchlist. All bot edits have been labeled yellow accordingly but Cluebot NG. Anyone know how to fix this? Chthe (talk) 10:56, 5 August 2025 (UTC)

ClueBot NG intentionally does not mark its reverts as bot edits, by general community consensus. This is because unlike most bots, vandalism reversion has a higher chance of incorrect edits—no bot is 100% accurate about determining vandalism—and we as a community want the extra scrutiny on those reverts that the watchlist provides. — Naomi Amethyst 22:30, 13 August 2025 (UTC)

It appears there is a secondary IRC feed channel for a bot named CBNGRelay-spam. The channel it is sending messages to is unregistered and the bot is not authenticated to any NickServ account. The feed it produces is generating a lot of spam alerts, so I have temporarily quieted it (+q) on the channel. Please evaluate whether this bot and channel needs to be in operation. If it does need to continue operation, work with the Wikimedia Group Contacts to register the channel with ChanServ, ensure that the bot authenticates to NickServ using SASL when connecting, and ensure that the bot is automatically given either voice or ops in the feed channel via the ChanServ +V or +O flags, respectively. Once you've done all of those things, feel free to remove the quiet on the bot. Skizzerz (talk) 16:18, 6 August 2025 (UTC)

@Skizzerz: On what channel? Never mind, @DamianZaremba: was messing around with the feeds... should be all good now - Rich^T|C|E-Mail 16:29, 6 August 2025 (UTC)

This should be authenticated (I grouped "CBNGReview" (https://cluebotng-review.toolforge.org), "CBNGRelay-spam" / "CBNGRelay-revert" / "CBNGRelay-debug" (https://github.com/cluebotng/botng) to the same nickserv account that "CBNGRelay" (https://github.com/cluebotng/bot) is using earlier today).

The production account uses #wikipedia-en-cbngfeed & #wikipedia-en-cbngrevertfeed, with the staging account using #wikipedia-en-cbngfeed2 & #wikipedia-en-cbngrevertfeed2.

The main different on staging is each channel uses it's own IRC client instance to try and avoid flood killing that regularly happens on the production account.

Essentially those channels should be registered and the bot granted access, the same as the production channels have... I can't do that right now as I don't have op in the channels. Alternatively I can disable the IRC feed on staging, though I do check this every now and then to compare activity. - Damian Zaremba ^{(talk • contribs)} — Preceding undated comment added 17:09, 6 August 2025 (UTC)

@DamianZaremba: The group contacts should be able to register it on your behalf and give you ops. Alternatively for -cbngfeed2 if you disconnect the bot and then join the channel yourself you should be automatically opped since the channel was otherwise empty. If you're having frequent issues with being disconnected due to excess flood, send an email to support<at>libera<dot>chat and we can potentially work with you for an increased flood limit (you'll want to ensure that your bot has some form of internal rate-limiting first). If you have further questions feel free to send me a PM on IRC as well and I'd be happy to chat there, I'm currently using the nickname awoo. Skizzerz (talk) 17:30, 6 August 2025 (UTC)

Thanks for the info.

Added basic SASL support in https://github.com/cluebotng/botng/commit/6b5f571130c6ae84607116bc0eaa8c4bd5562e4f (as is the case in the Python version); we where relying on NickServ before.

Registered the 3 channels and gave the accounts voice, inline with the production accounts.

It would be good to dig into the rate limits, we do have some very basic time window based implementation, though now we have more options on tools for runtime we could re-write the relay component to improve this furthur. Unfortunately I don't have time to get into this for the next couple of days, but will try and cycle back to it.

You are always free to ping me (if online on IRC I'm DamianZ, or here), otherwise Rich does a good job of messaging me on other platforms to get my attention. - Damian Zaremba ^{(talk • contribs)}

Looks like the flag changes didn't happen. You'll want to give the account +V (uppercase) in ChanServ (via the FLAGS) command for each of the channels. --Skizzerz (talk) 18:36, 6 August 2025 (UTC)

Ah, I did VOICE via ChanServ but that doesn't persist on reconnection. Added FLAG for each channel now. - Damian Zaremba ^{(talk • contribs)} 21:36, 15 August 2025 (UTC)

Requesting semi protection for saiyaara film page as too many unverified edits and vsndalism is effecting it. 120.61.228.243 (talk) 04:51, 14 August 2025 (UTC)

Wrong place... you want WP:RFPP - Rich^T|C|E-Mail 10:05, 14 August 2025 (UTC)

I’ll prepend this - as far as I can tell CBIII is not down - I’m just having issues on one particular page!

I’ve been trying to help User:CHCBOY set up archiving on his talk page, as it was getting rather unwieldy… however, so far nothing has been happening, even after a few days. I did spot one mistake in the template a few days ago and corrected it, but still nothing… any ideas? Danners430 _{tweaks made} 16:35, 17 August 2025 (UTC)

I didn't see anything obviously wrong, but your |format= was not quite how yearly was meant to be set up, and might have been the source of the issue, so I changed that. It may or may not fix the issue, we'll see Aidan9382 _(talk) 17:38, 17 August 2025 (UTC)

Fingers crossed! On a different point, an archives box seems to have now appeared, which I would say is undesirable given the tall header template already gives archive navigation… any clue where that’s appeared from? Danners430 _{tweaks made} 17:40, 17 August 2025 (UTC)

Actually I’ve just taken a look, and that format is one of the defaults… User:ClueBot III#Example: By year and numbered (with archive box) Danners430 _{tweaks made} 17:45, 17 August 2025 (UTC)

Huh, interesting. Normally I just see raw yearly and monthly, so in that case I'm not too sure what the issue could be. Also, the box has appeared due to |archivebox=yes from Special:Diff/1306037201 Aidan9382 _(talk) 18:22, 17 August 2025 (UTC)

Ah - I thought that only controlled archive boxes on the archive pages? Danners430 _{tweaks made} 18:34, 17 August 2025 (UTC)

I just happ need to look at WP:CR and noticed there were a few old completed discussions. It doesn't appear that Cluebit has archived any since the 7th. I've looked but can't see any changes that would've caused an issue, any ideas? -- LCU ActivelyDisinterested «@» °∆t° 20:21, 17 August 2025 (UTC)

Could this maybe be related to the discussion directly above? Is CB actually working at all? Danners430 _{tweaks made} 20:26, 17 August 2025 (UTC)

It's last edit was yesterday, CR hasn't been archived since the 7th. So I think this one at least is page related. -- LCU ActivelyDisinterested «@» °∆t° 20:39, 17 August 2025 (UTC)

Gotcha :) Danners430 _{tweaks made} 20:42, 17 August 2025 (UTC)

I'm starting to think this is bot related - usually it edits enough to fill an entire 500 page of contributions in just a day, but now it's done only about 50 in over a week. Something's probably broken somewhere, I'm just not sure where exactly Aidan9382 _(talk) 06:31, 18 August 2025 (UTC)

Worth pinging the maintainers an email? Danners430 _{tweaks made} 06:48, 18 August 2025 (UTC)

Looking at the history I think I was wrong about it being page related, you're right about it's edit history. Seems to have been editing fine until about 14:00 on the 7th, but after that there are gaps of hours if not days. -- LCU ActivelyDisinterested «@» °∆t° 11:42, 18 August 2025 (UTC)

I've asked Damian to give it a poke - Rich^T|C|E-Mail 12:55, 18 August 2025 (UTC)

It's hard to look back as we only have access to the last 1 hour of logs currently, but from the metrics the bot has been running very close to its CPU quota (an increase around the 7th). The health check has been restarting the bot after long periods of not editing (24 hours) but it has just been slow. It's currently executing a run at the 'usual' speed, I will check back on it later. - Damian Zaremba ^{(talk • contribs)} 13:58, 18 August 2025 (UTC)

Fixed a fatal error when running on PHP 8, which should help it complete the run. - Damian Zaremba ^{(talk • contribs)} 15:04, 18 August 2025 (UTC)

That would definitely cause issues :D Many thanks for all your support here! Danners430 _{tweaks made} 15:36, 18 August 2025 (UTC)

WP:Close should be sorted (tested that by hand hence the rollback earlier). Pretty sure things are working again now. Logged some issues ( https://github.com/cluebotng/cluebot3/issues ) for later. Feel free to ping me if things seem off in the next days (Rich will also keep an eye). - Damian Zaremba ^{(talk • contribs)} 22:12, 18 August 2025 (UTC)

Thanks Damian, and Rich. -- LCU ActivelyDisinterested «@» °∆t° 22:17, 18 August 2025 (UTC)

Andrew MacGregor Marshall hates UK monarchy and BBC edit by reliables source from Czello 113.53.162.32 (talk) 08:37, 22 August 2025 (UTC)

Please report this bot from Error program 2804:14C:5B41:85D7:4D6D:FDAB:A290:4B54 is Write all articles about Thai protest and andrew Marshall by using VPN in Thailand to edit page 113.53.162.32 (talk) 08:44, 22 August 2025 (UTC)

Please let me know if this is the wrong place to post, but I have had issues with Cluebot recently, either being quite inconsistent or simply not archiving my talk page. I have since tried to tweak the template after reading the documentation more thoroughly, but both the date archive function and archive now function seem to not be working anymore on my page.

I did manually archive the last two items on my talk page since this issue arose! I would appreciate it if somebody more familiar with the bot and the template quirks could take a quick look at my talk page.

Thanks sksatsuma 10:51, 22 August 2025 (UTC)

The Achilles' heel of this bot is that it's not very consistent with timing. It just comes around to archiving things "eventually". I love this bot for its features, but in its last archiving, it was 15 days late for me. If you want archiving to be done as soon as possible, probably use User:Lowercase sigmabot III. Aaron Liu (talk) 20:44, 26 August 2025 (UTC)

ClueBot III has incorrectly archived all active discussions on Wikipedia:Closure requests twice today. Another editor said they pinged the authors after the first instance. The emergency bot shutoff button lead me to the block page, so I blocked the bot for 3 days in the hopes this will be long enough for the authors to notice the problem and either fix it or disable this activity so the page doesn't keep getting blanked. -- Beland (talk) 17:39, 26 August 2025 (UTC)

@Beland It looks like perhaps this change changed how the bot interpreted the commented out archivenow parameter on that page, correctly parsing it as an empty string now. Any section that contains any of the archivenow strings will be forcibly archived during the next run. Every section contains the empty string, and so every section was archived. The page should be corrected to not have an empty archivenow parameter, and I'll see about making the bot to treat an empty archivenow string as the default setting. — Naomi Amethyst 22:09, 26 August 2025 (UTC)

Thanks for the diagnosis. I have updated the page to not comment out the desired archivenow parameter. However, because the strings have double curly braces, the bot will need to handle nowiki tags correctly. By correctly, I mean only looking at the contents of the <nowiki>...</nowiki> structure and not at the nowiki start and end tags. (Discussions that use nowiki tags should not be archived now.) -- Beland (talk) 01:50, 27 August 2025 (UTC)

@Beland: The bot documentation (archivenow) shows an example of what should follow archivenow=. There should be no comment—just nowiki tags. I might be missing something as I not familiar with the archiving syntax but it appears that Wikipedia:Closure requests had undocumented wikitext which you have now corrected. Why should the bot remain blocked? It might be argued that a blank archivenow value (after stripping whitespace) should be interpreted as "never archive now" but the way to achieve that would be to omit the archivenow parameter altogether. Johnuniq (talk) 05:39, 27 August 2025 (UTC)

Sure, it sounded like there might be other pages with the same problem that a bot code tweak would be needed to avoid. However, a live regex search doesn't show any, so I'm unblocking. Hopefully bot maintainers can take it carefully from here. Thanks for the quick response and the useful bot! -- Beland (talk) 07:56, 27 August 2025 (UTC)

That change was made to fix instances like https://github.com/cluebotng/cluebot3/issues/21, https://github.com/cluebotng/cluebot3/issues/23 and others where the config is very badly interpreted (written). While true that this broke a page (apologises for that) the new behaviour is actually that which is documented (default empty string, with <!-- --> being well documented as a comment). Being careful sometimes means robbing Peter to pay Paul, free to log any logic issues or contribute at https://github.com/cluebotng/cluebot3 - Damian Zaremba ^{(talk • contribs)} 15:08, 27 August 2025 (UTC)

While I was looking at the archive configuration for WP:Bot requests, I found that someone tried to add {{done}} and {{BOTREQ|done}} a while back, but someone else removed it after a few days because they didn't want those to trigger immediate archiving. What do you think of the possibility of adding two parameters like archivesoon and archivesoonage, where if one of the strings from archivesoon is present then archivesoonage is used in place of age for that section? For example, if a page is configured like this

{{User:ClueBot III/ArchiveThis
|age=1440
|archivenow=<nowiki>{{archive now}},{{tlu|User:ClueBot III/ArchiveNow}}</nowiki>
|archivesoon=<nowiki>{{done}}</nowiki>
|archivesoonage=48
}}

then sections would be archived after 60 days normally, but immediately if {{tlu|User:ClueBot III/ArchiveNow}} is there or after only 2 days if {{done}} is used in the section. Anomie⚔ 14:50, 3 September 2025 (UTC)

@Anomie: If you happen to have a GitHub account, can you throw this request on the issues page for CB3? - Rich^T|C|E-Mail 17:21, 4 September 2025 (UTC)

Ok. https://github.com/cluebotng/cluebot3/issues/26 Anomie⚔ 19:30, 4 September 2025 (UTC)

Why did you revert my edit [1]? I was TRYING to correct a possible vandalism from someone else. Don't do that again! 2600:880A:2504:9180:F15A:D30D:3C57:1A50 (talk) 19:25, 28 August 2025 (UTC)

At the top of the page, it clearly says the user here is not human. It can't read your message, much less answer questions or obey your demands. It's a dumb robot, even though using "AI". The edit you did was to remove a table entry -- that itself is a very common form of vandalism (or can be a good edit). You have very little known editing history. At a guess, those things were part of how the bot came to guess that your edit itself was vandalism. The bot is carefully tuned to remove an edit if it has a 99% chance of being right and a 1% chance of being wrong. It happened to be wrong in your case. The edit summary it left says what you can do to report such a "false positive". - R. S. Shaw (talk) 00:32, 31 August 2025 (UTC)