| 20:32.30 | *** join/#infobot infobot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 20:32.30 | *** topic/#infobot is Welcome to the infobot channel || Latest version: 1.5.3 @ https://sourceforge.net/project/showfiles.php?group_id=2241 || SVN: http://infobot.svn.sourceforge.net/svnroot/infobot/ || The original infobot is no more, it has been replaced by the latest version of blootbot, accompanied by a rename back to infobot || apt/ibot/infobot/jbot/purl is now an infobot |
| 20:32.30 | *** mode/#infobot [+o infobot] by ChanServ |
| 20:32.31 | TimRiker | s/support/suppose/ |
| 20:33.09 | troubled | TimRiker: did someone +q the bot? |
| 20:33.22 | troubled | +q/+b or +m channels prevent nick changes iirc |
| 20:33.41 | TimRiker | not that I know off, but possibly. |
| 20:34.06 | troubled | those are the only ways to prevent nick changes on freenode I think, unless I missed one |
| 20:34.44 | troubled | its intentional though, designed to help keep trolls from changing nicks to avoid kicks when they misbehave |
| 20:35.31 | troubled | generally, you end up in a channel like ##overflow if you reconnect during a split, which is usually +m. most likely what happened with the bot |
| 20:36.21 | troubled | well, assuming you overstep the join throttling limit on the channel and its setup +f #anotherchan, as well |
| 20:37.14 | troubled | TimRiker: errr. I mean, can you please submit a feature request to sf.net? ;) |
| 21:14.36 | TimRiker | :) |
| 23:12.07 | troubled | TimRiker: hmm, seen your reply in the bug list. Wasn't the identify command only for dcc or something? |
| 23:12.53 | troubled | I can't remember if I was looking maybe at only the DCC version of the 2 files though. But i thought something didn't work right for identification |
| 23:12.57 | TimRiker | troubled: also private message. |
| 23:13.06 | troubled | so it does work? |
| 23:13.30 | troubled | tbh, ive never tried identify since it always recognized me |
| 23:13.32 | TimRiker | yes. it works on infobot. I have 'A' set though. might not work without that. |
| 23:13.48 | troubled | something else for the todo list :) |
| 23:14.14 | TimRiker | identify just adds a mask. really need a whoami or similar. There might be something like that in there. |
| 23:14.17 | TimRiker | infobot: whoami |
| 23:14.17 | infobot | you are timriker, or n=timr@pdpc/supporter/bronze/TimRiker on #infobot and it's 2008.08.01. Don't believe me? Ask drfontus! |
| 23:14.21 | troubled | what do you think about the google bug? he reopened it |
| 23:14.46 | wyre | interesting |
| 23:14.48 | TimRiker | it's not a google bug. it's user error trying to add a factoid that starts with a command name. |
| 23:14.50 | troubled | "Don't believe me? Ask drfontus"? |
| 23:15.06 | TimRiker | ~literal whoami |
| 23:15.06 | infobot | "whoami" is "<reply> you are $who, or $user@$host on $channel and it's $date. Don't believe me? Ask $randnick!" |
| 23:15.14 | wyre | cute |
| 23:15.19 | TimRiker | :) |
| 23:15.30 | troubled | TimRiker: yes, but should it be reopened? or should we just remove the google hooks as per the mailing list entry? |
| 23:15.51 | troubled | I just need to know what the final official stance is on google searching with all the api key problems and TOS issues |
| 23:16.01 | TimRiker | I'd really like to get google scraping working sometime, I've just not gotten to it. |
| 23:16.27 | troubled | even though its kinda against TOS to have non bot owners query the entry? |
| 23:16.49 | wyre | noted one can search google via sms, is there a way to to do fafe sms requests... |
| 23:16.52 | troubled | a while back I tried the scraper, but I just couldnt get it to work |
| 23:17.03 | troubled | fafe sms? |
| 23:17.03 | wyre | s/fafe/fake/ |
| 23:17.05 | TimRiker | even though. yes. it's NOT automated use of google. think of the bot as a browser with an irc interface. |
| 23:17.37 | troubled | TimRiker: perhaps a +G (google) chattr flag or something to restrict use? |
| 23:17.49 | troubled | I would really hate to peeve google :) |
| 23:18.35 | TimRiker | heh. not real worried about it. I don't see anyone getting enough requests through the irc flood limits to make any difference to google. |
| 23:18.51 | troubled | no arguments there :) |
| 23:19.24 | wyre | i'd be surprised if there was much fuss, other bots do the scrapeing thing, /me sits down to watch some more |
| 23:19.25 | TimRiker | it would have a chanset entry so it can be enabled/disabled on a channel basis already. |
| 23:19.43 | troubled | true |
| 23:19.51 | TimRiker | ~chanset google |
| 23:19.51 | infobot | Showing google values on all channels... |
| 23:19.51 | infobot | <PROTECTED> |
| 23:19.51 | infobot | End of list. |
| 23:20.15 | TimRiker | I forget the current flag name... google, Google, w3search, who knows... |
| 23:20.38 | troubled | I don't know. I already don't like the case sensitive chanset stuff |
| 23:21.01 | TimRiker | me neither. all chanset flags should be lower case, and then convert .chan on read. |
| 23:21.06 | troubled | would you care if I removed the case sensitivity for 1.5.4? |
| 23:21.14 | TimRiker | please do! :) |
| 23:21.20 | troubled | :) |
| 23:21.36 | TimRiker | ~chanset W3Search |
| 23:21.36 | infobot | Showing W3Search values on all channels... |
| 23:21.36 | infobot | <PROTECTED> |
| 23:21.36 | infobot | End of list. |
| 23:21.37 | troubled | btw, I released 1.5.3 today |
| 23:21.45 | TimRiker | I think that's the one.. |
| 23:21.56 | TimRiker | good for you! :) |
| 23:22.06 | TimRiker | still not replied to lenzo... :( |
| 23:22.13 | troubled | I did today actually |
| 23:22.44 | troubled | as for 1.5.3, seems it was stable enough and the bug for addressing and "how are you" seemed to be a good reason. plus work kinda stalled for a bit |
| 23:24.42 | troubled | btw, do you remember what that left over bug was for multi nick that affected you from last month or so? |
| 23:32.05 | troubled | simonrvn: is the "Simon++" in CommandStubs.pl from you for the google search? |
| 23:52.11 | TimRiker | troubled: don't recall the multi-nick issue. |
| 23:52.59 | troubled | it was something that I forgot to consider with multi nicks and the Chan: ....., wasnt it? |