Minor refactoring ;)

Had a bug that when a tab is backgrounded, setInterval does not guarantee that the function will be called after the exact right amount of time. Using setInterval with an interval of 1000msec only means that the callback won't be called within 1sec. It could be 2sec, or 3sec... In particular, when a tab is backgrounded, Chrome won't fire the timers promptly. Since each tick subtracts one second, slower ticks means longer times.

For that reason, after each tick, I set a lastTick variable. On each tick, it looks at lastTick and subtracts the number of intervening seconds to now. That ought to fix things.

In the process of fixing the bug, I did a minor overhaul of the whole things.

Is the latest version deployed? Why don't I see the images on timetimeti.me?