The pull request says Elsewhen thinks in time zones, and a time zone is not a place. It says someone in Fort Lauderdale cannot find Fort Lauderdale, so they get “here in New York”, New York's weather, and a home pin a thousand miles north. It says a row also cannot say who it is for, because the label is what gets geocoded, so renaming Amsterdam to Emir would look up the weather for Emir.

The pull request says place search asks Open-Meteo's geocoder, the same keyless service the weather already uses. It says offline zone matches still come first.

The pull request says clicking the “here in …” header, or pressing w, opens Where are you? over any place. It says picking a place on this machine's zone updates the header, the globe's home pin, and the row that stood for the old here. It says that on another zone, it also moves the system clock through the same passwordless sudo timedatectl set-timezone rule the timezone menu uses. It says that clock change was not run on a live machine, and that the sudo rule allows it without a prompt.

The pull request says a row can name the people in it, on a line under the city. It says plain names get a monogram. It says a GitHub handle brings the profile's name and avatar.

Hughes wrote that remembering who is in a region was the hard part, so he made it easy to add people, and that updating your location in Elsewhen syncs that with the system clock.