IRC Logs for #circuits Sunday, 2015-09-13

prologicwe're not there yet :)01:08
prologicwe fly out on Sat01:08
*** koobs has quit IRC01:36
*** Coldblackice has quit IRC08:15
*** Coldblackice has joined #circuits08:15
prologicsucks not having a chair09:53
*** koobs has joined #circuits11:48
kdbYo koobs11:48
*** Coldblackice has quit IRC12:00
prologickdb, unload greeting13:32
kdbUnloaded plugin: greeting13:33
*** kdb has quit IRC13:34
*** kdb has joined #circuits13:34
*** kdb has quit IRC13:34
*** kdb has joined #circuits13:34
prologickdb, plugins13:34
kdbPlugins: google help autoid channels weather reconnect keepalive web stats ctcp dnstools irc webapi core spell broadcast eval logging swatch rss jsonrpc identified rmessage timers hello13:34
riotheya.. is it a good idea to implement a watchdog that notices when things go awry? And if so, has anyone done something like that? If not, any hints on implementation?17:07
riotthis thing could do other goodies: implement and transmit/store crashreports, last action logs, os stats and whatnot17:08
spaceonejay… python3.5 has been released today17:26
spaceoneb'%s' % (b'foo',) / b'{}'.format(b'foo') is back17:27
*** Coldblackice has joined #circuits17:58
*** Osso has joined #circuits20:03
prologicriot, yeah seems a good idea20:23
prologichave I written on using circuits; no (not yet)20:24
prologicshoudln't be hard though :)20:24
prologicI think I'm planning on writing one for autodock thougvh :)20:24
prologicwhich is writen using circuits20:24
*** Coldblackice has quit IRC20:29
*** Osso has quit IRC21:02
*** Coldblackice has joined #circuits21:17
riotprologic: i assume it should run as "external" as possible (i.e. the other running stuff shouldn't be able to take it down)21:27
riotwith the balance of it needing to see/know when things go awry21:28
*** An_Ony_M1ose has joined #circuits22:30
*** An_Ony_Moose has quit IRC22:34
*** billsb has joined #circuits23:06
*** billsb has quit IRC23:15

Generated by 2.11.0 by Marius Gedminas - find it at!