Re:Storing UTC is not a silver bullet (2019)
by netsharc on Sunday March 13, 2022 @08:30AM
(#30660663)
Interestingly, technically the time of the event changed with the hypothetical TZ law changes. The event was going to be n hours from now, but with the TZ law change, it got moved to be n+1 hours away.
If the convention hall could be booked hourly and had different events every hour, suddenly a slot would've opened up, at the 2 AM on the DST-change Sunday, the hour which would've not existed if the daylight savings law stayed the same...
Re:Storing UTC is not a silver bullet (2019)
by VMtest on Sunday March 13, 2022 @08:55AM
(#30660827)
> If the convention hall could be booked hourly and had different events every hour, suddenly a slot would've opened up, at the 2 AM on the DST-change Sunday, the hour which would've not existed if the daylight savings law stayed the same...
I did not think of this before...interesting....leave these problems to politicians, software engineers and end users to accommodate, I just want to be a naive programmer
Re:Storing UTC is not a silver bullet (2019)
by RubenvanE on Sunday March 13, 2022 @08:25AM
(#30660632)
The creator of https://hackerdaily.io here!
The reason for a timezone specific RSS feed is because, like the site itself, the RSS feed only updates once a day at midnight. And _when_ the day changes depends on the timezone. Therefore we created different RSS feeds, one for each time zone.
I think 3 days ago I was checking on it again, because I was wondering how websites put timestamp in their published RSS/atom feed
https://hackerdaily.io RSS feed made me confused, to select timezone for the RSS feed as they want to think "Yesterday" means different thing for different timezone, not sure why, but I don't want to confused myself thinking how timezone and "Yesterday" work together
HN is using UTC, I realized that by hovering the mouse pointer on the "2 hours ago"
Again, if people don't want to use UTC for future events it's their choice. Personally I would advocate to use UTC and manually calculate the local datetime for future event, even if local timezone changes
You know, I wonder how watches work in this case, how do you alter the time on your watches according to the DST changes? The mechanical engineer of the watch takes this bug into account?