Quote from: tacoLover7916 on 07/23/2020 08:08 pmMy bet is that the site has a single time that it does the time change from standard to DST. Perhaps the site uses the last Sunday of March as many European countries do. Since Boca Chica changed its time on the second Sunday of March as the US does, leaping ahead one hour, this would make sense of the discrepancy. In Boca Chica the time was an hour ahead because it had changed to DST already but the site hadn't realized the change.That's consistent with a quick look at the underlying forum code -- it uses the system's default DST transition rules and then adds in your offset from GMT, rather than trying to use a client-dependent, client-supplied set of rules for DST transition.What's odd is that if I add "%Z" (timezone name) and "%s" (UNIX/POSIX timestamp in decimal) to the Time Format string in the Profile, it displays "BST" as a timezone but displays times consistent with UTC/GMT:Current forum time: 2020-07-23, 20:55:27 (BST: 1595537727)while on my end if I ask for London time I get:TZ=Europe/London date +"%Y-%m-%d, %H:%M:%S (%Z: %s)"2020-07-23, 21:56:55 (BST: 1595537815)which is British Summer Time (UTC+1)
My bet is that the site has a single time that it does the time change from standard to DST. Perhaps the site uses the last Sunday of March as many European countries do. Since Boca Chica changed its time on the second Sunday of March as the US does, leaping ahead one hour, this would make sense of the discrepancy. In Boca Chica the time was an hour ahead because it had changed to DST already but the site hadn't realized the change.
Quote from: launchwatcher on 07/23/2020 08:59 pmQuote from: tacoLover7916 on 07/23/2020 08:08 pmMy bet is that the site has a single time that it does the time change from standard to DST. Perhaps the site uses the last Sunday of March as many European countries do. Since Boca Chica changed its time on the second Sunday of March as the US does, leaping ahead one hour, this would make sense of the discrepancy. In Boca Chica the time was an hour ahead because it had changed to DST already but the site hadn't realized the change.That's consistent with a quick look at the underlying forum code -- it uses the system's default DST transition rules and then adds in your offset from GMT, rather than trying to use a client-dependent, client-supplied set of rules for DST transition.What's odd is that if I add "%Z" (timezone name) and "%s" (UNIX/POSIX timestamp in decimal) to the Time Format string in the Profile, it displays "BST" as a timezone but displays times consistent with UTC/GMT:Current forum time: 2020-07-23, 20:55:27 (BST: 1595537727)while on my end if I ask for London time I get:TZ=Europe/London date +"%Y-%m-%d, %H:%M:%S (%Z: %s)"2020-07-23, 21:56:55 (BST: 1595537815)which is British Summer Time (UTC+1)I think that's because it uses the offset you have set in your profile as a hack on top of using Europe/London for timezone information.
Idea: why don't we do on NSF the same thing as we do on all spaceflight, human and satellite: use UTC. Gives one time stamp for all spaceflight related events, for everyone around the globe. When local times matter, like local launches from Florida or Guiana or Satish Dhawan, it would make only a single adjustment to UTC rather than the multiple ones required to get times from two local timezones synced up, given disparate political daylight savings rulz, etc.
I've found that the simplest thing to do is when the timestamps on posts are not correct is to go to Profile > Modify Profile > Look and Layout. Then I click "(auto detect)" next to the Time Offset and it gets changed to the needed value to make the timestamps correct.I find that I need to do this more than just twice/year.
The issue is that if you're in the US then when you look at old posts from the middle of March the timestamps are one hour off while the posts for the rest of the year have correct timestamps. Those in timezones whose daylight savings time changes are the same as the UK's will not see this issue. The same is presumably true for posts from a few weeks in the fall between the end of Summer Time in the UK and the end of Daylight Savings Time in the US.
Quote from: Ken the Bin on 07/24/2020 11:24 pmI've found that the simplest thing to do is when the timestamps on posts are not correct is to go to Profile > Modify Profile > Look and Layout. Then I click "(auto detect)" next to the Time Offset and it gets changed to the needed value to make the timestamps correct.I find that I need to do this more than just twice/year.The issue isn't with the time for current posts. That can be fixed by changing the time offset value.The issue is that if you're in the US then when you look at old posts from the middle of March the timestamps are one hour off while the posts for the rest of the year have correct timestamps. Those in timezones whose daylight savings time changes are the same as the UK's will not see this issue. The same is presumably true for posts from a few weeks in the fall between the end of Summer Time in the UK and the end of Daylight Savings Time in the US.
Quote from: ChrisWilson68 on 07/24/2020 11:32 pmQuote from: Ken the Bin on 07/24/2020 11:24 pmI've found that the simplest thing to do is when the timestamps on posts are not correct is to go to Profile > Modify Profile > Look and Layout. Then I click "(auto detect)" next to the Time Offset and it gets changed to the needed value to make the timestamps correct.I find that I need to do this more than just twice/year.The issue isn't with the time for current posts. That can be fixed by changing the time offset value.The issue is that if you're in the US then when you look at old posts from the middle of March the timestamps are one hour off while the posts for the rest of the year have correct timestamps. Those in timezones whose daylight savings time changes are the same as the UK's will not see this issue. The same is presumably true for posts from a few weeks in the fall between the end of Summer Time in the UK and the end of Daylight Savings Time in the US.The period of innacuraccy isn't just in March. It's any time that British Daylight Savings time is not in affect.
UTC is also known as GMT for Greenwich Mean Time
At different times in the past, it has been calculated in different ways, including being calculated from noon;[1] as a consequence, it cannot be used to specify a precise time unless a context is given.English speakers often use GMT as a synonym for Coordinated Universal Time (UTC).[2] For navigation, it is considered equivalent to UT1 (the modern form of mean solar time at 0° longitude); but this meaning can differ from UTC by up to 0.9 s. The term GMT should not thus be used for certain technical purposes requiring precision.