FYI we have this information locally in libtimezonemap already and an algorithm specified for querying this for ubuntu-system-settings (https://wiki.ubuntu.com/TimeAndDate#Choosing_locations - scroll down a bit "Whenever").
I think it might make sense for libtimezonemap to implement this algorithm itself, then the three locations that need it that I know of (two in unity-control-center datetime, one in ubuntu-system-settings) could all call the same API.
Maybe there were good reasons for using the server (such as localised search?) that we don't know about atm. Would need to investigate.
FYI we have this information locally in libtimezonemap already and an algorithm specified for querying this for ubuntu- system- settings (https:/ /wiki.ubuntu. com/TimeAndDate #Choosing_ locations - scroll down a bit "Whenever").
I think it might make sense for libtimezonemap to implement this algorithm itself, then the three locations that need it that I know of (two in unity-control- center datetime, one in ubuntu- system- settings) could all call the same API.
Maybe there were good reasons for using the server (such as localised search?) that we don't know about atm. Would need to investigate.