Probably time zone differences.
But the forum post was at 20:19:10UTC, with an edit at 20:27:31UTC according to the forum
Before anyone asks, I have my time offset in my profile settings to 0, and this also matches my computer's UTC clock as well.
Quote from: ThreadSnake on 07/22/2020 05:29 pmBut the forum post was at 20:19:10UTC, with an edit at 20:27:31UTC according to the forumQuote from: ThreadSnake on 07/22/2020 05:29 pmBefore anyone asks, I have my time offset in my profile settings to 0, and this also matches my computer's UTC clock as well.This site doesn't give you timestamps in UTC. It gives them in your local time. Just because you set the current offset from UTC to zero doesn't mean it is giving you UTC for past posts. It probably assumes you're in a time zone that observes daylight savings time that just happens to currently have a zero offset from UTC but a one-hour offset from UTC at other times of year.The forum only lets you specify the current offset from UTC. It doesn't let you set something like an Olsen name that would include daylight savings information. But I've noticed that I don't have to change anything when the daylight savings change happens in my location, the forum just adjusts my offset automatically.I don't know how it's deciding the daylight savings time rules for your account, but I think it is deciding them for you. Maybe it gets it from your browser. Maybe it uses your IP address to infer a location. Maybe it just assumes based on your UTC offset. I don't know. But I think the evidence suggests the timestamps it's giving you include daylight savings.
If it was inferring that I am in daylight savings time, wouldn't displayed times be one hour ahead?(I am in the northern hemisphere in the US observing local time EDT at the moment)
Quote from: ThreadSnake on 07/22/2020 06:48 pmIf it was inferring that I am in daylight savings time, wouldn't displayed times be one hour ahead?(I am in the northern hemisphere in the US observing local time EDT at the moment)If it thinks you are currently observing daylight savings and it thinks your current offset from UTC is 0 hours, then it believes that during non-daylight-savings times of year you are one hour behind daylight savings. So when showing you a timestamp that is noon UTC it would tell you it's 11:00am in your local time. If you interpret that 11:00am as being UTC, the timestamps would seem to you to be 1 hour before the times they actually represent.
Quote from: ChrisWilson68 on 07/22/2020 07:05 pmQuote from: ThreadSnake on 07/22/2020 06:48 pmIf it was inferring that I am in daylight savings time, wouldn't displayed times be one hour ahead?(I am in the northern hemisphere in the US observing local time EDT at the moment)If it thinks you are currently observing daylight savings and it thinks your current offset from UTC is 0 hours, then it believes that during non-daylight-savings times of year you are one hour behind daylight savings. So when showing you a timestamp that is noon UTC it would tell you it's 11:00am in your local time. If you interpret that 11:00am as being UTC, the timestamps would seem to you to be 1 hour before the times they actually represent.That is a good theory, but the problem in this situation is that the posts in question are also posted in times of the year where daylight savings time exists in the US.
I think you could be on to something. I will try changing my offset to -6 and see if it changes the relative difference.
Quote from: ChrisWilson68 on 07/22/2020 07:05 pmQuote from: ThreadSnake on 07/22/2020 06:48 pmIf it was inferring that I am in daylight savings time, wouldn't displayed times be one hour ahead?(I am in the northern hemisphere in the US observing local time EDT at the moment)If it thinks you are currently observing daylight savings and it thinks your current offset from UTC is 0 hours, then it believes that during non-daylight-savings times of year you are one hour behind daylight savings. So when showing you a timestamp that is noon UTC it would tell you it's 11:00am in your local time. If you interpret that 11:00am as being UTC, the timestamps would seem to you to be 1 hour before the times they actually represent.The two examples in your original post are from dates in March that are after daylight savings starts in the US but before it starts in the UK and other parts of Europe. Since you told it your offset from UTC is zero, it could well be assuming you're in a European time zone where you are currently in UTC because of daylight savings but in mid-March you were one hour behind UTC because you weren't in daylight savings then.
One semantic nit: It is Daylight Saving Time, not Daylight Savings Time. In this context saving serves as a verbal adjective, while savings is a verbally derived noun, e.g. savings is what you have in the bank.Think of it this way, is the Heimlich a life savings maneuver or a life saving maneuver?
Although the singular form daylight saving time is the original one, dating from the early 20th century—and is preferred by some usage critics—the plural form is now extremely common in AmE. [...] The rise of daylight savings time appears to have resulted from the avoidance of a miscue: when saving is used, readers might puzzle momentarily over whether saving is a gerund (the saving of daylight) or a participle (the time for saving). [...] Using savings as the adjective—as in savings account or savings bond—makes perfect sense. More than that, it ought to be accepted as the better form.
I want to gather more information on what posts/times of the year this occurs, to get a larger dataset to analyze. I will make some more posts on here once I have that information, but for now, I will be using any other sources I can find linked to the events I'm researching.
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.