There seems to be an issue with the clock and timezones. I did some 1 hour in China today and when landing in Sweden i changed to Swedish timezone. The clock is counting up but when i leave the study page and then go back again the clock goes back to approximately 63 minutes all the time. I did a couple of 10 minute sessions but all the time i where back on 63 minutes when i did go back to the study page. Is there any caching involved here? When i changed the timezone it where a new day in China so the counter had started over for a new day when i changed back to Swedish time.

There is a "feature" here.
- I did practice in Chinese timezone
- When landing in Sweden I did some more practicing until i remembered to change timezone in Skritter. At this time skritter where on a new day. When changing timezone I did get back to the day before.

The result of this is that the Skritter clock do properly count the time while on the study page but when you leave and come back it will revert back to 1 hour 2 minutes and 58 seconds. However, today when it is a new day in Sweden as well and I do some skrittering, the clock do not start at 0 but on 28 minutes that is the total time i did study yesterday but did not count on yesterday. Seems that once skritter have changed to a new day it is cached and if i then change timezone it still remembers that but do not show the time to me in all situations. No problems, now that I know that I am fine with this.

I had some really wonky stuff the last time I flew internationally - I Skrittered randomly through the day before and after the flight, and since I flew east across the date line, I was logging time for the same day for something like 42 hours... Then it weirded me out even more when it kept on the same day past midnight PST.

Actually, I seem to remember Nick said something about the day resetting at 4 AM for Skritter, presumably because some people stay up past midnight but few get up before 4 AM. I guess that solves the mystery, but with all that jet lag I felt like something really weird had happened to Skritter, the day just kept going and going and going...

Haha, yeah, that makes sense. if you get some time assigned to tomorrow, then even if you switch timezone to get back to today, it'll always assign the time to the latest day, which is tomorrow, and load the initial time from the day corresponding to your timezone settings, which is today.

A better strategy would be to have everything either do it one way or the other, but I think it would slow down the code to be checking timezones when it saves review time to a day, and it would be more weird to always go with tomorrow for all the other things. So perhaps we'll leave it this way and confuse some more nomads.