It lives on infrastructure that is funded out of the pocket of a few guys who use it for completely different purposes (including myself), basically. The "silent involuntary" partners are guys who know me, but don't know anything about the site other than it exists and it lives on their server.

Ah, OK then. Good on them (and you too).

Just shut up and take the credit!

^ This :D

Had a feeling it wasn't Rogue who fixed it

Back in sync. Yeah!

Does it automatically update once Daylight saving starts?.......oops

Well done to....all. :D

The clock's out again.

Current time: 12.00

Post time: 2.00

Edited April 6, 201015 yr by titan_uranus

The clock's out again.

Current time: 12.00

Post time: 2.00

For some stupid reason the only way I can get it to display the correct time is by changing it to the time for Osaka in Japan. That solves the issue when you are not logged in. If you log in you need to change the time in your settings to Osaka time +9:00.

For some stupid reason the only way I can get it to display the correct time is by changing it to the time for Osaka in Japan. That solves the issue when you are not logged in. If you log in you need to change the time in your settings to Osaka time +9:00.

Better to try and find the root cause -- it's not particularly practical to have everyone change their timezone, and doing that could bugger everyone's time up again later when the actual problem magically fixes itself (you only need to review the rest of this thread to see this happens sometimes ).

The place to start would be finding out what the time on the server clock is.

For some stupid reason the only way I can get it to display the correct time is by changing it to the time for Osaka in Japan. That solves the issue when you are not logged in. If you log in you need to change the time in your settings to Osaka time +9:00.

Done that. I don't think everyone will want to do that, though.

Better to try and find the root cause -- it's not particularly practical to have everyone change their timezone, and doing that could bugger everyone's time up again later when the actual problem magically fixes itself (you only need to review the rest of this thread to see this happens sometimes ).

The place to start would be finding out what the time on the server clock is.

Agree. Not that I know anything about this kind of thing, so I have no idea how time-consuming/difficult it would be to fix. But there must be some way to fix it.

The issue has been fixed now. If you have your time in your settings set to Melbourne (or whichever timezone you are in) time then it should display the correct time now.

There hasn't been a change for Daylight Savings. Or is that me?

Bump.