5 ms·
> ... but as of 22:28 UTC Facebook appears to be ... Someone assumed London==UTC, when London is 1 hour ahead :) that was actually 21:28 UTC
by ruoso 5y ago
> ... but as of 22:28 UTC Facebook appears to be ...
Someone assumed London==UTC, when London is 1 hour ahead :) that was actually 21:28 UTC
- interestica 5y agoNo matter what time of year it is, people tend to use 'EST' for 'Eastern Time' even when we might be in Eastern Daylight Time rather than Standard. It's especially annoying when dealing with multiple countries that may or may not be using Daylight Saving Time.
- Wolfspirit 5y agoEven google isn't quite sure about the summer time. Not sure if that is just a Google German thing... A few weeks ago I tried to find out what the current time in CET is. Asking google for "CET" gave me: "23:27 CET". Asking google for "CET time" (I know that "time" is twice in this case) gave me "00:27 CET". The last one is wrong and should be CEST or even more correct would be just the same result for CET as I asked for
- imglorp 5y agoI am always forgetting the polarity. Seeing the cut-overs listed helps me: $ zdump -v Europe/Berlin | grep 2021 Europe/Berlin Sun Mar 28 00:59:59 2021 UT = Sun Mar 28 01:59:59 2021 CET isdst=0 gmtoff=3600 Europe/Berlin Sun Mar 28 01:00:00 2021 UT = Sun Mar 28 03:00:00 2021 CEST isdst=1 gmtoff=7200 Europe/Berlin Sun Oct 31 00:59:59 2021 UT = Sun Oct 31 02:59:59 2021 CEST isdst=1 gmtoff=7200 Europe/Berlin Sun Oct 31 01:00:00 2021 UT = Sun Oct 31 02:00:00 2021 CET isdst=0 gmtoff=3600
- Jamie9912 5y agoIn this case, Google is providing a wrong answer to not confuse people. People don't understand that a time zone can exist but not be observed at the same time
- delecti 5y agoI make a point to give local times in just "PT". Not least among my reasons is that I can't ever remember which half of the year is Daylight time and which is Standard.
- Wolfspirit 5y agoTimezones are the most annoying thing... right after encoding
- doublerabbit 5y ago> right after encoding No joke. Today I ended up writing a whole essay explaining the issue I was having and almost sending it off to the core developers because I thought I had discovered an issue with the actual language. The bug was because I had forgot to convert too&from utf-8 in these two procedures: proc 2Hex { input } { binary encode hex [encoding convertto utf-8 "$input"] } ;# Converts base32 string data to base16 proc 2Base { input } { encoding convertfrom utf-8 [binary decode hex "$input"] } ;# Converts string hex data to base32 On the plus side, I now have written documentation of the internals of my program.
- VBprogrammer 5y agoOh TCL. I didn't miss you.
- paxys 5y agoI personally find timezones more annoying. At least with encoding once you figure things out it will work indefinitely. Timezones can simply change from under you with or without notice.
- remram 5y agoUnicode 14 just came out. If you are using collation, NFD, ... you need to update your libs.
- ethbr0 5y agoYou think timezones are simple, and then you realize this, when you try to implement them (in the US): https://en.wikipedia.org/wiki/Time_in_the_United_States#Boundaries_between_the_zones https://en.wikipedia.org/wiki/Time_in_the_United_States#Boun... (And that's not counting daylight savings time, and its varied observance!)
- gcbirzan 5y agoActually, the article seems to confuse the times quite a lot. It's talking about ~16:50 UTC at points, but the outage started at 15:40, which they not only mention in the article but you can also see on the graphs.