3 ms·
> If it’s not already configurable It's not. > If it’s not already configurable then it had to be replaced in 2007 when we last changed the start of DST. Yup
by mlyle 5y ago
> If it’s not already configurable
It's not.
> If it’s not already configurable then it had to be replaced in 2007 when we last changed the start of DST.
Yup, both these systems are about 10-15 years old.
- pishpash 5y agoMore than these exceptions, gadgets nowadays like to be IoT's and use internet time servers. The blast radius on things made since 2007 is likely smaller than you think.
- mlyle 5y agoUsing internet time servers is largely the problem, because then you need to take UTC and make it into a useful local zone.
- pishpash 5y agoInteresting, you're right. However does that not present a backdoor by setting up a local time server to proxy changes? It's a hack but ... a solution.
- jedberg 5y agoIt depends on what it asks for. If it asks for “current time in PDT” or “current time in PST” it just returns the same answer. If it asks for UTC and does the conversion locally, then we’re back to the original problem of being able to update the switchover date which changes all the time and should be updateable.
- jedberg 5y agoWell then to be fair you’d have had the same problem if they just changed the start date again. And the last time the start date was changed we only had 18 months to adjust. It’s not like these changes are rare edge cases — it happens all the time. So hopefully as you replace the system you find a vendor who writes good time code!