EarthNow v2.6.0

Release notes

A feed EarthNow cannot read no longer wipes its events

If a source changed the shape of its feed so that none of its events could be read, EarthNow used to take that as the source having nothing to report: its events vanished from the globe, the copy kept for offline use was overwritten with nothing and the source was shown as fresh and healthy. Now such an answer counts as a failed fetch for USGS, EONET and the volcano report alike. The last good events stay on the globe and on disk; the provider status says what went wrong and when the next attempt is.

The status says when some events could not be read

When a source's answer holds items EarthNow cannot use, the provider status panel now says how many; the status button shows its dot. Before, that count reached only the log.

A cache warning goes away once saving works again

If the events could not be saved for offline use (a locked file, say), the warning used to stay for the rest of the run even after later saves succeeded. It now clears on that source's next good save. A warning about one source is no longer replaced by another's; each is shown until its own source saves again.

Raising the minimum magnitude applies at once, even offline

Choosing a higher minimum magnitude in Settings used to leave smaller quakes on the globe until USGS next answered, which never happened while offline and carried over to the next start. The globe now shows only quakes at or above the minimum straight away. The smaller ones are still kept on disk, so lowering the minimum again brings them back without a fetch.

Every request stays on https and on its own source

EarthNow already refused to follow a redirect to any host outside its list. It now also refuses any request or redirect over plain http, so event data cannot be sent unencrypted where it could be altered on the way. Each source also has a connection of its own that reaches only its own host, so one source's redirect can no longer reach the cloud or burnt-area service while that layer is hidden. If you have set a proxy in the HTTPS_PROXY environment variable, EarthNow's requests go through it, as before; the documentation now says so.