This could be exploited to force the default config, which has a 60s offline grace period during which connectivity could be restored.
Idea: On config retrieval failure, set offline grace period and warning grace period to zero. This config must make any use impossible.
Question: How to recover? Currently we just leave the config at defaults. We should probably retry loading the config. It seems safe to assume that while we can't do that, we can't report activity either.
This could be exploited to force the default config, which has a 60s offline grace period during which connectivity could be restored.
Idea: On config retrieval failure, set offline grace period and warning grace period to zero. This config must make any use impossible.
Question: How to recover? Currently we just leave the config at defaults. We should probably retry loading the config. It seems safe to assume that while we can't do that, we can't report activity either.