Joe Wilm

That would be nice to have

Thanks for the heads up! This link should work in the mean time.. http://blog.jwilm.io/chatbot/chatbot/

@rmbreak way better

Oh shoot! Somehow missed this go by on my feed :flushed:. We should probably replace all of the `println!` statements with the log macros as you've suggested. Looks like the...

@emk Thanks for sharing that you've ran into the same thing. This may be as simple as reconnecting in the slack library's [`on_close` handler](https://github.com/jwilm/chatbot/blob/master/src/adapter/slack/mod.rs#L74) which is currently a noop for...

@emk The panic was from the openssl library which is not directly included by the slack library. It's depended on by the websockets library which slack uses. The panic issue...

That sounds like the right place to start. I'm heading out for a few hours, but I will check in on this later.

Just to summarize the status here: - Chatbot w/ slack adapter crashes in openssl. Dependency chain is chatbot > slack-rs > rust websockets > openssl. - The chatbot program will...

@emk looks like `thread::spawn` returns a `thread::JoinHandle`. Calling `join` on the handle returns a `Result` which is an `Err` if the thread had panicked. The stack guard would only need...

The initial trait I had in mind was something like: ``` rust trait Brain { fn set(key: &str, value: Json); fn get(key: &str) -> Json } ``` Since that would...