Daniel (dB.) Doubrovkine

+1 on reducing the assumptions about storage - I think the first step would be to extract a storage interface

Take a look at https://github.com/slack-ruby/slack-ruby-bot-server/pull/38, build on top of that.

If you look at how this bot framework is constructed you have hooks, such as [message](https://github.com/dblock/slack-ruby-bot/blob/master/lib/slack-ruby-bot/hooks/message.rb) that respond to anything, and then it's all the way up from there trying...

I think relying on the return of the method is going to make it very hard to debug for people and also has potential to break backward compatibility. Generally my...

This is really a Slack API question, but looking at `chat_postMessage` it looks like this is controlled by the value of `broadcast`? Try setting it to `false`? https://api.slack.com/methods/chat.postMessage#arg_reply_broadcast

This is really a Slack API question, I don't know more than the documentation [here](https://api.slack.com/rtm#real-time-messaging-rtm-api__sending-messages). The `say` [implementation](https://github.com/slack-ruby/slack-ruby-bot/blob/7c1c0265a144c948a2b9410cb7ea5dbf5e95df16/lib/slack-ruby-bot/client.rb#L60) is a dumb wrapper. I would switch to `chat_postMessage` and call it...

I think you could just implement the re-install workflow and succeed in that case instead of raising an error?

@amar-sharma You definitely don't want to reimplement the endpoint and maintain 2 URLs, just get rid of the exception. But you can't remove it, its original intent is to avoid...

https://github.com/slack-ruby/slack-ruby-bot-server/blob/99e91edbc3092dc9f9665fb8c9be3eebff3252f1/lib/slack-ruby-bot-server/models/team/methods.rb#L15 does not do what you think it does, it marks the team inactive, doesn't shutdown the connection, etc. In your own code I *think* it's safe to just remove...

> I don't mind either way, it just makes more sense to me to have the variable as the noun of what it is, like `teams_table` or `activerecord_teams_table` Except that...