News for hackers. Stuff that matters.

A comment on It's Time for a Change: Datetime.utcnow() Is Now Deprecated. Parent comment

Re:It's Time for a Change: Datetime.utcnow() Is Now Deprecated by albert_e on Monday November 20, 2023 @02:54AM (#38344186)
Yes if the meeting host is in a country that does not observe DST/summertime ... then this problem kind of solves itself. Then only those whose local clock dances around the year need to dance around to match :)

Outlook and calendar apps should probably make this a feature: "do not move this meeting for DST/summertime" (even if the host is in US/EU). Make it opt-in initially and a couple of years later make it opt-out (default) choice.

On a lighter note ... recurring meetings tagged to "dynamic time zones" should be allowed only after hosts "agree" to a disclaimer that they have consulted other participants and have their consent :D (a little like recording with two-party consent)

[ Parent | on HN ]
Re:It's Time for a Change: Datetime.utcnow() Is Now Deprecated by tsimionescu on Monday November 20, 2023 @03:25AM (#38344627)
You seem to put very heavy emphasis on the precise recorded time of a recurring meeting in everyone's calendar. In my experience, this is mostly irrelevant: the time of a recurring meeting is often renegotiated when circumstances change for a big enough swathe of participants, such as schedule changes in the more northern/souther latitudes as winter&summer approach.
[ Parent | on HN ]