I believe it's because the client/server protocol is still deficient. I'm trying to squeeze out the time to fix it
On 30 March 2011 11:11, James Purser <[email protected]> wrote: > That sounds like it could be the issue. Refreshing the page brings up the > correct date/time > > On Wed, Mar 30, 2011 at 9:45 AM, Kai Chang <[email protected]> wrote: > > > Not familiar with the code-- but it may be a Javascript bug. JS uses > > milliseconds instead of seconds for Unix time, so you need to multiply > > regular Unix time by a thousand. > > > > On Tue, Mar 29, 2011 at 3:39 PM, James Purser <[email protected] > > >wrote: > > > > > Doing some testing I've noticed that the time and date for "other > > > participants" (ie not your participant) is still being given as 1970, > Jan > > > 1. > > > > > > Where abouts in the code is this and is anyone else seeing it? > > > > > > -- > > > James Purser > > > Collaborynth > > > http://collaborynth.com.au > > > Mob: +61 406 576 553 > > > Wave: [email protected] > > > > > > > > > -- > James Purser > Collaborynth > http://collaborynth.com.au > Mob: +61 406 576 553 > Wave: [email protected] >
