00:25:46 <[Tritium]> ChrisWarrick: in the US and Canada, you know your timezone as US/Eastern or Canada/Eastern etc. You dont think of time in terms of what other city is in the same time zone as you. God help you if you are in the mid west - it would be easy to pick the wrong city 00:33:38 <[Tritium]> And if you are in indiana, you might as well source your time from /dev/urandom 08:38:48 <ChrisWarrick> [Tritium]: Ubuntu’s installer apparently disagrees 08:42:07 <[Tritium]> Ubuntu's installer is not a halmark of exceptional design. The reason the aliases exist in the olsan DB is because americans dont think in terms of what major cities are in the same time zone as you are right now... we know eastern, central, mountain, and pacific 08:42:26 <[Tritium]> and that indiana and arizona are weird 08:53:49 <ChrisWarrick> macOS also does America/Toronto et al 09:04:26 <[Tritium]> does it have the full olsan DB? 09:04:59 <[Tritium]> because lacking Canada/Eastern would mean they edit the database 09:14:18 <ChrisWarrick> they have the full database, Canada/Eastern exists, but they prefer the cities as well 09:16:59 <ChrisWarrick> macOS in settings asks for a "nearest city", but their list is quite different from the cities in Olson 09:26:13 <[Tritium]> Thats in itself problematic... if I live in the suburbs west of nashvill, tn, then nearest city will give the wrong timezone 09:27:23 <[Tritium]> and if nearest city is used for anything other than timezone...setting to memphis isnt helpful either 09:29:54 <ChrisWarrick> The default setting is “Set time zone automatically using my current location”. macOS claims the closest city is the city I’m actually in (a very small town), but /etc/localtime points to Europe/Warsaw 09:31:01 <[Tritium]> so they are doing some more than rudimentary geolocation stuff