Jump to content

User talk:ClueBot Commons

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 76.22.118.146 (talk) at 22:51, 20 April 2017 (Click Here link broken: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The current status of ClueBot NG is: Running
The current status of ClueBot III 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 ClueBots' owner or someone else who knows the answer to your question will reply on this page.

Template:Archive box collapsible

ClueBots
ClueBot NG/Anti-vandalism · ClueBot II/ClueBot Script
ClueBot III/Archive · Talk page for all ClueBots
Beware! This user's talk page is monitored by talk page watchers. Some of them even talk back.

...is down. ««« SOME GADGET GEEK »»» (talk) 05:03, 3 April 2017 (UTC)[reply]

As are the IRC feeds. West.andrew.g (talk) 17:14, 3 April 2017 (UTC)[reply]
And oddly enough, CBNG itself is running. —k6ka 🍁 (Talk · Contributions) 12:15, 4 April 2017 (UTC)[reply]
CB III (archiving), on the other hand, is down. ~ Rob13Talk 12:20, 4 April 2017 (UTC)[reply]

IRC is still down. I will ping the operators. Thanks, West.andrew.g (talk) 13:37, 6 April 2017 (UTC)[reply]

After a couple day fix, IRC is down again. West.andrew.g (talk) 14:10, 10 April 2017 (UTC)[reply]
... and back again. I'm going to put the old cronjobs back in place as it seems bigbrother is not great at restarting things when needed. Apologies for the interruption, I was away with a laptop that was lacking the SSH key to fix this. - Damian Zaremba (talkcontribs) 20:20, 14 April 2017 (UTC)[reply]

All the while ClueBot NG's false positive report page is still not up. Get ready to handle lots of false positive reports below... ««« SOME GADGET GEEK »»» (talk) 20:23, 14 April 2017 (UTC)[reply]

Still down. Should we be putting false-positive reports here in talk in the meantime (I've got this one to report), or waiting until it's back up? Ibadibam (talk) 04:20, 17 April 2017 (UTC)[reply]
I've been dockerizing and kubifying all of my more recent personal projects, and it's turned out to be really stable. Perhaps it is time to dockerize CBNG and CB3 and move them off wmflabs and on to my Kubernetes cluster. Both CBNG and CB3 were written back in the day before I was willing to pay for hosting, as I was in college and had no money, and the reliability shows. CB3, at some point, should be updated to fix a bunch of the bugs with it. I'm still a huge proponent of the algorithm that CB3 uses to archive threads (based on history, and backlinks), but the code and the execution of that algorithm is lacking, and needs some major cleanup. CBNG's code, however, is still quite clean; it's just the supporting services (report/review interfaces, infrastructure surrounding it) that seem to be less reliable. @DamianZaremba: we should discuss this in the next few weeks. -- Cobi(t|c|b) 05:52, 17 April 2017 (UTC)[reply]

.... ClueBotNG, You are correct of ten bulls, I must have been mistaken by believing I should Pick Fruit through Tai-Chi, and taste this ancient Peach. Perhaps the mistake was an accord as well, for the Vitality of water and the sweetness of Japanese Plumb has overpowered me with it's tart nature, for This poem is not of the down, but of the East. The western way would also try for this unifying cause! https://en.wikipedia.org/wiki/Fusang — Preceding unsigned comment added by 184.53.48.126 (talk) 23:53, 17 April 2017 (UTC)[reply]

A question.

It seems that Cluebot III and Cluebot NG are slowly falling into code-disrepair. As Wikipedia changes, so does vandalism. Meanwhile, Cluebot NG isn't detecting 40% (Roughly) of vandalism. Yes, Cluebot NG makes our lives easier, but i think it's time for a rewrite. Also, Cluebot III is just... Yeah. Maybe it's time to deactivate Cluebot III and create a new, fully updated version of it similar to how the original Cluebot got deactivated in favor of Cluebot NG. Terrariola (talk) 10:45, 6 April 2017 (UTC)[reply]

@Terrariola: ClueBot NG doesn't need a code rewrite, just needs to have its database of edits updated for recent vandalism trends. CBNG was designed to learn and adapt over time.
As for CBIII... there's lowercase sigmabot III, which has stood the test of time well. —k6ka 🍁 (Talk · Contributions) 12:45, 6 April 2017 (UTC)[reply]
I agree both the bots need improvements, but sadly the 'life' things gets in the way via consumption of large amounts of time. All the code is opensource on GitHub and I'd be happy to review any suggested changes. Moving the report interface to use oauth and bringing the review interface back is long over due. - Damian Zaremba (talkcontribs) 20:18, 14 April 2017 (UTC)[reply]

False positive

I couldn't find the link, so I wanted to tell you that your revert to Burnin' It Down was a false positive, because I was removing a redlink. --2600:8805:2409:AB00:48C7:1E4:D06C:4085 (talk) 21:16, 8 April 2017 (UTC)[reply]

For the record, the link to the diff is here and the MySQL ID is 3000112. —k6ka 🍁 (Talk · Contributions) 01:16, 9 April 2017 (UTC)[reply]

ClueBot III

Out of curiosity, is there any reason that ClueBot III isn't running? Elisfkc (talk) 16:04, 11 April 2017 (UTC)[reply]

Apologies, it looks like the process stopped and the watcher failed to restart it. It should be back again now - Damian Zaremba (talkcontribs) 20:15, 14 April 2017 (UTC)[reply]

You archived that page ([1]) but the page has moved and no button to access that archive is on that "new" talk page. — Preceding unsigned comment added by 68.151.25.115 (talk) 07:47, 17 April 2017 (UTC)[reply]

I believe it should go to http://tools.wmflabs.org/cluebotng/ not http://tools.wmflabs.org/cluebot/ . 76.22.118.146 (talk) 22:51, 20 April 2017 (UTC)[reply]