Daniel (dB.) Doubrovkine

I am open to this, however I think what we're all saying is that we want multiple DSLs on top of similar infrastructure. Some people want a command DSL, some...

IMO anything on a deprecation path should not be used for anything new. I think something more specific to Rails and that is compatible with https://github.com/slack-ruby/slack-ruby-bot-server-events might make more sense?

> What does that optimally look like? What's the most efficient way to get there? I think it's a fork of https://github.com/slack-ruby/slack-ruby-bot-server-events that takes a Rails dependency instead of slack-ruby-bot-server.

This is a dup of https://github.com/slack-ruby/slack-ruby-bot/issues/75, but let's keep it open since it has a lot of detail.

I am down with an explicit declaration. This could be similar to Rails or to Grape where the order declared is the order processed. I believe that would require deprecating...

Please submit a PR.

> I need to enable socket mode on a new internal slack application. I'm curious to know if you've made any progress on implementing this yet, as well as if...

- `apps.connections.open` definitely belongs in slack-ruby-client - socket mode specifics likely belong in an extension similar to https://github.com/slack-ruby/slack-ruby-bot-server-rtm

Without debugging I am going to guess that it's reconnecting, and re-registering commands when that happens. I'll take a look when I get a chance.

Reconnect happens in slack-ruby-client with a ping worker. There's a lot of detail in https://code.dblock.org/2019/03/04/solving-slack-side-disconnects-in-slack-ruby-client.html with links. But I think the problem here is simpler and is something about the...