Misty
I wonder just how many systems are going to get confused or choke on my province's new time zone. I guess people have six months notice before it really becomes an issue
Mar 18 at 5:05pmWeb
Show threadKlaus FrankMar 18

@misty

Tbh, I don't understand why not every it system just uses UTC internally and leaves all of the timezone crap up to the fronted as "fancy formatting".

That would solve so many issues that are caused by the systems running in local time and then having to constantly convert it when interacting with other shit that is configured to a different local time...

Show threaddamien 🥖🐈‍⬛🧣Mar 18
@agowa338 @misty i mean, the frontend, whatever it is, still needs to *know* about the timezones so that's just moving the problem
Show threadKlaus FrankMar 18

@eramdam @misty

Well it would remove the most annoying problems like e.g. the apple calendar not being able to handle an appointment with start time in UTC+1 timezone and end time in UTC+8 in combination with daylight savings. And then showing the appointment at a different time than MS Teams is showing it.

Show threaddamien 🥖🐈‍⬛🧣Mar 18
@agowa338 @misty ...i guess? idk it all depends on the implementation, storing dates with offsets/iso string isn't a wrong idea, what matters is how they're handled when computing things and such
Show threadKlaus FrankMar 18

@eramdam @misty

Well the funny thing is it actually stores them as such in the .ica file.

Hence why I come back to what I said initially all systems should just use UTC internally and leave the timezone part to the frontend.

You're in India? Time shown on the frontend in your local time but stored as UTC.

Then someone in Europe opens that file and the dates get formatted according to their local time. But the time stored in the file is still UTC.

Basically way less potential for fuckups...

Show threadYoh DeadfallMar 18
@agowa338 @eramdam @misty, it's a partial solution while the problem is in humanity and in thoughts that time is simple. Look, we have time zones and daylight saving time, and no system handling it correctly. And I even haven't started about realtime and monotonic clocks!
Show threadKlaus FrankMar 18

@yoh @eramdam @misty

Well the main issue is that people using time in file formats and such thought "time is simple". If they assumed it is complex they'd have abstracted it and just normalised it all along...

Show threadDavid Fi&erMar 18
@misty Everybody with a thermostat is so screwed.
Show threadAmgineMar 18

@misty

UTC-7 has been around a long time, as has Mountain Time, and Pacific Daylight Time.

People using America/Vancouver may be screwed, though.

Wish we were on UTC-8 / PT.

Show threadJune!Mar 18
@misty Skimming the tzinfo mailing list (Discussed across a handful of threads https://lists.iana.org/hyperkitty/list/[email protected]/) it seems like a 2026b zoneinfo release is coming fairly soon
tz - lists.iana.org

Show threadJessica🏳️‍🌈Mar 18
@misty I already created a custom "Pacific Time (British Columbia)" zone for my Win98 machine lmao
Show threadSn4ptr4nMar 18
@misty Subscribing to [email protected] for entirely unrelated reasons