FYI: There are currently severe storms in the area. If the power (or networking) goes out there may be an outage of Metasmoke and SmokeDetector Osiris. Backup power supplies protect against power flickers, but won't guard against a full outage for more than 20-30 minutes
^^ power's flickering here something fierce so, thought i'd get the notice up
i'll standby Osiris if i lose power for more than a few minutes ('cause at that point the entire infra will be going into 'time to shut down for safety' mode
@ThomasWard Yep. We'd still want an SD instance active in order to report into chat, but one of the standby instances should be fine to use for that (which is why they exist :) ). The worst case is that we just don't have an active SD instance for a while. Second worst case is that we don't have one until one of the other people who can run an instance manually start one. But, you already know all that...
OTOH, we should probably have code which results in the standby instances coming active when they can't contact MS, which would allow users to give them commands, perhaps a timed period of being in standby (or an alternate way for SD instances to communicate with each other, which could be used to coordinate standby/active when MS isn't availalbe).
@Xnero I don't know. I know that not all the people running them are in the US. Where the other instances are physically located is rarely of concern, and might change with little or no notice. As far as I'm aware, the instances other than Osiris are hosted in the cloud, which means they could be moved to any of multiple server farms located in various areas of the world.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
