Daniel (dB.) Doubrovkine

We could use something first class, subclassing `Event` or `InteractiveMessage`. Right now you'd have to roll your own API handlers. Examples: Events: https://github.com/dblock/slack-strava/blob/master/slack-strava/api/endpoints/slack_endpoint.rb#L86 Interactive Messages: https://github.com/dblock/slack-strava/blob/master/slack-strava/api/endpoints/slack_endpoint.rb#L66

There's nothing special in this gem for those, feel free to contribute.

That makes sense @Startouf, feel free to contribute.

Should this just be a README section? Someone care to PR? Another option is to implement `client.reply`, but I don't like having to pass `data` in, so some wrapping should...

Doc added in https://github.com/slack-ruby/slack-ruby-bot/commit/162b9e04dffb52fb45c2ff4118e80c009cbf404f

I don't know what exception class is raised in the error above, but if it was a `Faraday::Error` it's now handled in https://github.com/dblock/slack-ruby-bot/commit/06b721fa99b05e93ab2551b0f7dbe616e106d8ec. Leaving it open until confirmed.

Slash commands are not supported out of the box, partly because this is usually implemented with a web front-end. I'll label this as a feature request though.

Not really. You have all the parts to build it there though. What I'd like is a DSL and documentation on how to support slash commands in slack-ruby-bot. Implementing something...

No, please feel free to contribute @mabdelfattah.

I think this is a reasonable approach. Selection via attachments works just fine, you can see an example [here](https://github.com/dblock/slack-sup/blob/master/slack-sup/models/sup.rb#L39) that is handled [here](https://github.com/dblock/slack-sup/blob/master/slack-sup/api/endpoints/slack_endpoint.rb#L13). There's also easy all-in-one daemon support, checkout...