@JF I don't doubt that it could be dead, since it is 3 years old and ties together two APIs, but it is still working fine for me right now.

It's been located at stackgeography.apphb.com for a while now. There were a few links in there that worked, but I hadn't updated them all. When the custom domain came up for renewal, I let it go.

Thanks for the feedback. The repeat was by design, since I couldn't guarantee where the viewer would be located. I didn't want to pin someone into a corner of a continent-centric layout. Unfortunately, this caused that marker issue to arise that you noticed. If two flags for the same item are visible, Google Maps highlights one of them regardless of which one is actually clicked. I haven't nailed down if this is something I am doing, but I am suspecting the Google Maps system does this by default.

@systempuntoout When AppHarbor started charging for using a custom hostname, the domain stopped resolving. I hadn't been back here in a while, but it has been forwarding correctly for a while now.

@matcheek All the geocoding is done with Google Maps API, but I proxy it through a server-side DB cache since the app was hammering Google directly for every person for a very limited number of unique user locations. After running for most of three months, there are only 790 entries in said cache (oddly, only 18 entries that didn't geocode).

In case you check it out again, I added multiple-site polling. All selected sites from the list of checkboxes (vs. the old radio buttons) is still a saved preference.

I definitely have that planned for where there are far more preferences to be set. Until I get the chance to really incorporate savings of preferences, I did a stripped-down version. While it doesn't assume you want to start polling, it does save/load your chosen site from localStorage when it is available in the viewing browser. After you have a setting saved, it should auto-select; just wait for the selection window to pop and smash the enter key to start polling.