Or if config.webconverger.com is down for an extended period of time.
Currently the status quo is that it will reset to defaults after 15 seconds of trying.
Noticed that we are checking for a new live config on every restart of the browser which can be slow.
Perhaps we should just concede for simplicity sake if the config wasn't grabbed at boot, it needs a reboot?
Or we could have a construct like updates.sh where it runs in the background every ten minutes?
Our current stance is that it's simpler and easier to ask folks to reboot on configuration change.