| 01:31.45 | rorx | DocScrutinizer05: it looks like you can identify yourself to an infobot by password, instead of by netmask.. would that work even if there is no matching netmask, I assume? Also is the password that goes it the info file, the literal password, or is that cypher text of some kind? |
| 01:34.55 | DocScrutinizer05 | sorry, no idea |
| 01:35.21 | DocScrutinizer05 | infobot is maintained and owned by TimRiker |
| 01:35.50 | DocScrutinizer05 | I recall it was quite an adventure to get my account on bot working |
| 01:36.50 | rorx | DocScrutinizer05: yeah, I have only identified (implicitly) via the hostmask, but I'm on a temp connection, so wondered if there was another way to authenticate |
| 01:37.05 | DocScrutinizer05 | I don't know |
| 01:37.06 | rorx | guess I'll have to read source code.. |
| 01:37.30 | rorx | the examples in the users file look like it could by cyphertext |
| 01:37.32 | DocScrutinizer05 | I hardly know the commands for managing bot accounts |
| 01:38.11 | DocScrutinizer05 | ~botsnack |
| 01:38.11 | infobot | aw, gee, DocScrutinizer05 |
| 01:38.24 | rorx | yeah, it's not very well documented, to say the least.. ironically, I think Ken Lenzo's original infobot 0.4 documentation is the best attempt. |
| 01:38.43 | rorx | and I think his infobot site has recently gone offline. |
| 01:38.47 | DocScrutinizer05 | I seem to recall even Tim had problems |
| 01:39.40 | DocScrutinizer05 | like "meh! I dunno why that other stuff doesn't work, but the way it's now seems sufficent, so let's keep it like that" |
| 01:40.15 | DocScrutinizer05 | otherwise he prolly hadn't granted all permissions to me either ;-) |
| 01:41.43 | DocScrutinizer05 | plus I have an account with a ssh pubkey on his server which is limited to login command `infobot reboot` ;-) |
| 01:42.23 | DocScrutinizer05 | this plus the ~infobot help is basically all I know about that critter |
| 01:42.41 | rorx | ah I see.. |
| 01:42.41 | DocScrutinizer05 | never seen a config file |
| 01:42.59 | rorx | I have learned everything I know from reading Ken Lenzo's docs, and reading some of the source. |
| 01:43.37 | DocScrutinizer05 | wishes those Ken Lenzo's docs were still available |
| 01:44.04 | rorx | I had to fix a few bugs that were preventing the HEAD version from reconnecting on its own in some cases.. there is still one showstopper I think.. it doesn't rejoin a channel when it's forced to use it's secondary nick, on connect. |
| 01:44.22 | rorx | they should be, give me a sec. |
| 01:45.07 | DocScrutinizer05 | yeah |
| 01:45.11 | DocScrutinizer05 | known issue |
| 01:45.25 | DocScrutinizer05 | I tend to give the bot a reboot in such case |
| 01:46.30 | DocScrutinizer05 | I have infobot's 3 nicks on watched nicks list |
| 01:47.19 | DocScrutinizer05 | and usually there seems to be no way to make a missing impersonation of the three to reconnect when it fails during a netsplit or ping timeout |
| 01:48.06 | DocScrutinizer05 | I managed occasionally to talk to another nick to make it send commands to nickserv like "/msg nickserv regain" |
| 01:48.48 | rorx | hmm yeah, I only use one nick with mine, so not sure if the changes I made, broke that ability.. I was mainly trying to just get the one identity to reconnect on its own.. I think I was able to fix 2 of the 3 issues where it didn't |
| 01:50.25 | DocScrutinizer05 | would be great to send those patches to TimRiker |
| 01:51.02 | rorx | yeah, I thought of it, but as I said, I'm not sure that it didn't break the multi-identity feature.. figured it wouldn't be worth contributing them, until that is tested. |
| 01:51.03 | DocScrutinizer05 | he rants since ages that "scheduler needs a refactoring" |
| 01:51.57 | rorx | oh It's Kevin Lenzo, not Ken.. and it looks like he still has infobot.org registered. I may reach out to him via email and offer to host the site, if that's all that is needed. |
| 01:52.43 | rorx | DocScrutinizer05: ok, here's a recent version of the guide page from Kevin's original site.. http://web.archive.org/web/20071020035823/http://www.infobot.org/guide-0.43.x.html |
| 01:53.18 | DocScrutinizer05 | wow, thanks! |
| 01:54.18 | rorx | I think I ended up saving the archives of the last 0.4 release, and his last snapshot of the 0.5 version he was working on, before he gave up on the whole thing (and before Tim integrated the 0.4 features into blootbot) |
| 01:56.43 | rorx | but yeah, I think the most important thing to update, is what Kevin was actually working on for his 0.5 release.. and that is to switch out the perl Net::IRC module with the POE::Component::IRC module.. It's something I've hoped to do at some point, but I suspect it will take a significant amount of work. |
| 01:58.23 | rorx | But I suspect a lot of these re-connection bugs and such would be resolved by switching to POE::Component::IRC, as I think part of the problem with Net::IRC is that it doesn't always realize when it has timed out (forcing you to use another method to make that determination) |
| 01:58.43 | DocScrutinizer05 | meh, ignorelist woefully missing |
| 01:58.43 | rorx | But besides that, Net::IRC isn't even maintained anymore. |
| 01:59.46 | rorx | It's no longer in CPAN as a result. I've been running my infobot on a machine with perl 5.14, and am about to upgrade to 5.20.. I hope I can still build Net::IRC on that version, so I can continue to use the bot. |
| 02:00.29 | DocScrutinizer05 | pretty much no clue about that sort of stuff |
| 02:00.47 | DocScrutinizer05 | I hardly can *read* perl |
| 02:05.37 | rorx | I keep forgetting Tim's version is above 1.0, maybe those continue the blootbot versioning sequence |
| 02:28.19 | DocScrutinizer05 | ((ignorelist woefully missing)) ignore (w/o parameters) does the trick though |
| 02:29.43 | DocScrutinizer05 | rorx: another flaw or even bug: even when bot isn't in a chan anymore (evidently) it still lists a remembered number of users etc |
| 02:30.23 | DocScrutinizer05 | IOW there's no way to tell if the bot has lost /join status of a chan |
| 02:30.44 | rorx | DocScrutinizer05: hmm, what commands demonstrate that, seen? |
| 02:30.57 | DocScrutinizer05 | status |
| 02:31.03 | DocScrutinizer05 | chaninfo |
| 02:31.33 | DocScrutinizer05 | only witnessed it when a whole nick impersonation went down |
| 02:31.57 | DocScrutinizer05 | ~+cahnset apt |
| 02:31.59 | rorx | ah, speaking of seen, I think there's supposed to be a config directive that controls whether seen works on a channel (presumably) but in my experience it still tracks users on those channels where the config explicitly has seen disabled. |
| 02:32.03 | DocScrutinizer05 | ~+chanset apt |
| 02:32.03 | infobot | Showing apt values on all channels... |
| 02:32.03 | infobot | <PROTECTED> |
| 02:32.03 | infobot | End of list. |
| 02:32.42 | DocScrutinizer05 | even when apt is down, infobot still lists all those channels as joined |
| 02:32.51 | DocScrutinizer05 | ~+chaninfo |
| 02:32.51 | infobot | 124/124 channels, 4501 users, 3404 unique: #debian/1612, #kde/479, #gsoc/254, #asterisk/182, #devuan/172, #maemo/161, #wowuidev/147, #oe/123, #wowace/93, #neo900/79, #cubieboard/58, #harmattan/50, #arm-netbook/50, #bzflag/48, #wowhead/47, #meego/46, #qi-hardware/43, #elinux/42, #openmoko/42, #curseforge/42, #utah/41, #maemo-ssu/38, #asterisk-dev/36, #openmoko-cdevel/35, #webos-internals/35, #slug/24, #uphpu/23, #brlcad/23, #sc2mapster/22, ... |
| 02:33.45 | rorx | hmm, interesting.. yeah having supporting multiple identities with one instance, complicates the programming, as I recall |
| 02:34.02 | rorx | I'm not sure I've seen any other bot which supports that feature. |
| 02:34.21 | rorx | I wonder if that's a feature that was already there in blootbot |
| 02:38.27 | DocScrutinizer05 | no idea |
| 02:38.47 | DocScrutinizer05 | prolly needed when number of channels exceeded MAXCHAN |
| 02:39.17 | DocScrutinizer05 | slightly different topic: do you know what's "lobotomize" and what to use it for? |
| 02:39.53 | DocScrutinizer05 | ~rot13 timriker |
| 02:39.53 | infobot | gvzevxre |
| 02:40.02 | DocScrutinizer05 | ~seen gvzevxre |
| 02:40.04 | infobot | gvzevxre <~TimRiker@bzflag/projectlead/TimRiker> was last seen on IRC in channel #infobot, 500d 1h 5m 6s ago, saying: 'vivint line is back up'. |
| 02:40.25 | DocScrutinizer05 | what the... |
| 02:40.30 | DocScrutinizer05 | ~seen timriker |
| 02:40.31 | infobot | timriker <~TimRiker@bzflag/projectlead/TimRiker> was last seen on IRC in channel #bzflag, 61d 23h 13m 50s ago, saying: 'macsforme, the package description files should be updated. if they don't get updated, then they will still be lgpl. not a big deal, that's allowed.'. |
| 02:46.29 | rorx | nope don't know what lobotomize does. |
| 02:47.36 | rorx | actually there is a doc/USAGE, I see.. |
| 02:50.00 | rorx | USAGE mentions lobotomy, but not what it's used for. |
| 02:53.06 | rorx | ah, I see there are some pod files in there too.. gosh why didn't I see this before.. |
| 02:53.06 | DocScrutinizer05 | ~+help lobotomize |
| 02:53.25 | rorx | the password field in the user files is indeed cyphertext |
| 02:53.31 | rorx | crypt formatted, it says. |
| 02:53.31 | DocScrutinizer05 | ~+help lobotomy |
| 02:54.09 | rorx | hmm, odd, mine won't give me any help on lobotomy |
| 02:55.39 | DocScrutinizer05 | also any sort of docs regarding chan settings would be really great |
| 02:55.54 | DocScrutinizer05 | ~+chanset _default |
| 02:55.54 | infobot | Default channel settings |
| 02:55.54 | infobot | <PROTECTED> |
| 02:55.54 | infobot | <PROTECTED> |
| 02:55.54 | infobot | <PROTECTED> |
| 02:55.55 | infobot | <PROTECTED> |
| 02:56.25 | rorx | yeah, there is an infobot.config.pod for that purpose |
| 02:56.41 | rorx | doc/infobot.config.pod |
| 02:57.03 | DocScrutinizer05 | great! :-) hope I'll find my way through the repo(s) |
| 02:57.46 | rorx | run specify it as an arg to perldoc(1), and it'll generate man-page like output. |
| 02:57.57 | rorx | -run |
| 02:58.05 | DocScrutinizer05 | http://svn.code.sf.net/p/infobot/code/ already puzzles me to no end |
| 02:59.57 | DocScrutinizer05 | seems like I had to choose between a half a dozen branches(?) like infobot-old/ blootbot-www/ don/ poco-irc/ ... |
| 03:00.46 | rorx | I track the trunk, so HEAD |
| 03:00.49 | DocScrutinizer05 | trunk/ ? |
| 03:00.55 | DocScrutinizer05 | aah ok |
| 03:02.25 | DocScrutinizer05 | hah, great |
| 03:06.16 | DocScrutinizer05 | wow! =item B<set friendlyBots> [B<botname> [B<bot2> ... B<botN>]] |
| 03:38.04 | rorx | DocScrutinizer05: I don't think there's been a formal release of infobot, since Tim took it over, has there? |
| 04:50.05 | DocScrutinizer05 | prolly not |
| 04:50.21 | DocScrutinizer05 | I dunno though when he did take over |
| 04:51.11 | DocScrutinizer05 | [2016-12-02 Fri 07:08:47] *** The channel topic is " Welcome to the infobot channel || Latest version: 1.5.3 @ https://sourceforge.net/project/showfiles.php?group_id=2241 || SVN: 1.5.4 http://infobot.svn.sourceforge.net/svnroot/infobot/ || Blootbot merged into infobot || apt/ibot/infobot/purl run by TimRiker". |
| 04:51.13 | DocScrutinizer05 | [2016-12-02 Fri 07:08:47] *** The topic was set by TimRiker!TimRiker@bzflag/projectlead/TimRiker on 2012-08-16 Thu 01:17. |
| 05:54.44 | *** join/#infobot DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 10:53.48 | *** join/#infobot rorx (~rorx@cpe-74-130-27-145.kya.res.rr.com) |