Internet source of configured websites, or even all settings

OOOOhhhhh. Good idea here. What if we could specify the websites to use and maybe some other small settings on our github? That way it could just read that on boot up, if it exists, it uses those! If it's not set, then show the default!

That would be a big step to make this really reliable because then overlay can be turned on all of the time. You run the setup, specify the settings URL to injest, then once it's done, you turn on the overlay protection! No more power outage issues (this killed at least 2 of my setups so far)

The issue names no files, tests, or entry points. Start by locating the setup and boot-time configuration paths, then trace how website and overlay settings are currently sourced. Done should mean an optional remote settings source is read at startup, defaults remain available when it is absent, and settings survive power loss.

Written by the indexing model from the issue text.