Conversation with #inferno at Sun Nov  8 16:50:55 2009 on powerman-asdf@irc.freenode.net (irc)
(17:12:20) anothy_x [n=a@99.25.151.44] entered the room.
(18:17:42) Fish [n=Fish@AVelizy-152-1-75-62.w86-217.abo.wanadoo.fr] entered the room.
(20:00:58) anothy_x1 [n=a@adsl-99-25-151-44.dsl.bcvloh.sbcglobal.net] entered the room.
(20:10:08) anothy_x left the room (quit: Read error: 110 (Connection timed out)).
(21:54:58) anothy_x1 left the room (quit: Read error: 104 (Connection reset by peer)).
(22:02:07) anothy_x [n=a@adsl-99-25-151-44.dsl.bcvloh.sbcglobal.net] entered the room.
(00:13:06) Fish left the room (quit: Remote closed the connection).
(01:35:32) mycrofti1 [n=drabgah@h69-128-47-245.mdsnwi.dedicated.static.tds.net] entered the room.
(01:41:53) mycroftiv left the room (quit: Read error: 104 (Connection reset by peer)).
(02:12:35) mycrofti1 is now known as mycroftiv
(02:16:08) npe left the room (quit: ).
(03:23:12) sswam [n=sswam@CPE-121-220-96-239.lnse3.win.bigpond.net.au] entered the room.
(03:50:32) raiz left the room (quit: Client Quit).
(05:14:53) sswam left the room (quit: "leaving").
(05:20:22) me__ [n=venkates@c-68-55-179-48.hsd1.md.comcast.net] entered the room.
(06:52:38) rapidfx [n=host666@vl-cen-ce1.avtlg.ru] entered the room.
(06:55:36) anothy_x1 [n=a@adsl-99-29-33-241.dsl.bcvloh.sbcglobal.net] entered the room.
(06:57:51) anothy_x left the room (quit: Read error: 110 (Connection timed out)).
(07:12:03) anothy_x1 left the room (quit: Read error: 60 (Operation timed out)).
(07:21:17) sqweek [n=none@124-169-155-176.dyn.iinet.net.au] entered the room.
(11:14:33) gualteri [n=salva@crespins.disca.upv.es] entered the room.
(11:30:38) gualteri: morning
(11:31:20) sqweek: heya gualteri
(11:34:01) robot12: hi
(11:35:22) mjl-: morning all :)
(11:37:26) sqweek: mjl-: i think travelling has taught me something about timestamps, and question the wisdom of having them serverside
(11:37:55) mjl-: hehe, good point
(11:38:07) mjl-: i knew that problem would come up some time :P
(13:00:51) raiz [n=raiz@p4FE889AC.dip0.t-ipconnect.de] entered the room.
(13:10:16) uriel: abolish timezones!
(13:11:02) uriel: and I believe server-side timestamps are better, re-calculating them on the client side and adjusting timezones is a nightmare
(13:11:28) mjl-: hah
(13:11:43) mjl-: it doesn't have to be that bad
(13:12:27) mjl-: you can return timestamps relative to current time on the server side, and sum it with current time at client
(13:12:46) mjl-: no, problematic for ircfs, since timestamps are just part of the lines of text
(13:16:47) uriel: timestamps relative to current time? hmm... that is interesting...
(13:17:05) uriel: still feels a bit awkward, but maybe it is a good idea..
(13:17:35) mjl-: current time == time of read
(13:17:39) mjl-: styx read
(13:18:07) mjl-: so you store absolute times on server, turn them into relative time (relative to server current time) when packing the data in styx responses messages
(13:18:10) mjl-: should be accurate enough
(13:18:44) mjl-: but right now lines are stored in ircfs as array of byte, no way to get timestamp out of it.  but that's not hard to change.
(13:27:22) uriel: still seems way more complexity for what it is worth IMHO 
(13:28:44) mjl-: jups
(13:28:59) mjl-: plus, you could then to do it different per channel/user
(13:29:20) mjl-: i would usually want to see the time as the other user(s) sees it
(13:29:36) mjl-: so i know they are likely awake/asleep
(16:19:19) npe [n=npe@195.207.5.2] entered the room.
(16:34:04) mennis [n=mennis@adsl-065-012-170-146.sip.asm.bellsouth.net] entered the room.
(16:35:17) uriel: mjl-: seeing the time as the other user sees it might be useful, but really confusing too when you have many users, plus I don't think irc really gives you enough info for that