slack bot needs a backup

[syberphunk]

As far as I'm aware, there's currently only LHS_Slackbot on one server. To maintain consistency, slackbot should ideally have a backup on another server which is aware of when LHS_Slackbot goes down and can take over, then if/when lhs_slackbot comes back, either it maintains control and lhs_slackbot takes over when the opposite happens or relinquishes control.

[ultrafez]

I'd possibly generalise this point as "consider resilience". Whether that means a high-availability setup with two servers for fail over, or better mitigation on the one server we have. Generally speaking the bot isn't well designed for high availability, so effort could/should be put into understanding failure modes of the single instance of the bot and mitigating them.