Andrew wrote:
>
> But having the commits in localtime would solve the above for
> me with the added bonus of knowing what time it happened.

Commits in localtime may not be trivial to solve. Two values are needed:

- The commit time (known, easily obtained from the database, and already sent to the client browser).
- The hours difference between server time and client time. This is not a fixed value. For example, New Zealand is sometimes 13 hours ahead of PST and sometimes it's 15 hours ahead of PST. And it might even be 14 hours ahead at some times.

I'm hoping someone will code a solution, either server based or client based.