05:45:03 -!- Dabomber has joined. 05:46:07 Hi all 05:48:05 -!- Dabomber has quit (Client Quit). 07:59:59 -!- clog has quit (ended). 08:00:00 -!- clog has joined. 11:02:09 -!- tav has changed nick to tav|offline. 15:23:57 -!- Keymaker has joined. 15:24:11 hiya 15:24:47 my legs hurt, i've been standing and walking all the day.. 15:35:19 -!- Keymaker has changed nick to Keymaker|eat. 16:03:41 -!- Keymaker|eat has changed nick to Keymaker. 16:47:26 m'hi. 16:50:24 hi 16:50:41 dbc been around? 16:51:18 no 16:51:22 ok 16:51:52 wonder if I'm still actively ircing by the time you manage to catch him. 16:52:53 :) 16:53:00 'actively' 16:53:42 or, it can be he reads the logs and checks the times carefully; so that he can idle safely many hours and get out just before i join channel.. 16:54:50 erm, well.. I fail to see how anyone can deduce from the logs when you will appear. the other way it'd work; maybe _you_ are reading the logs and only join after he has left. 16:55:21 you're right 16:57:33 just small opinion: do you think program should ask 'are you sure you want to ..' things or just do something, or should there be something where user can set it to ask or deactive the feature? 17:00:18 well, generally speaking everything should be configurable. 17:00:22 i see 17:03:25 I doubt the 'are you sure you want to' dialogs even help much, if you're decided enough to screw up you'll manage to do that even if you have to click through dozens of warnings. 17:04:07 i've noticed that pretty well :) 17:04:58 *delete all the files?* *ok* *still want to delete them?* *yes* darn! :( 17:22:48 aaaargh, it's sauna, bye for a while.. 17:47:44 done 19:16:56 -!- Keymaker has changed nick to Keymaker|movie. 20:29:52 -!- Keymaker[-] has joined. 20:30:19 -!- Keymaker[-] has changed nick to Keymaker. 20:38:24 -!- Keymaker|movie has quit (Read error: 60 (Operation timed out)). 22:15:50 hmm, byes 22:15:50 -!- Keymaker has quit (Read error: 104 (Connection reset by peer)). 22:20:53 bye.