bug: Time zone causes undue session lock + displayed time is not in local timezone
Description of issue
When using LanguageLab from another time zone (e.g., I'm currently at GMT-5), when I start an "instant session," it is correctly started, but when I open it, it is locked and presented as a future session, and it prevents me from writing.
Likely explanation
I suspect the input locking mechanism to be dependent on the USER time, rather than the SERVER time.
Proposed fix
- Use SERVER time (or universal time/GMT) to decide whether the session is open/current or past/future/locked.
- (and/or make sure the session is open to writing multiple hours before the planned starting time)
- Check if USER time is not used unduely elsewhere.
- Present the session time in LOCAL user time (here, if I start a session now at 22:00 GMT-5, it is shown as 5:00 am tomorrow [=GMT+2]).