This only works with "classic" slack apps

[leetrout]

I think the README should be updated to indicate it uses the RTM API which does not function with new slack apps that have granular oauth permissions.

Took me 40 minutes to figure out what was going on by finally dropping the debug option in the config and seeing:

slack-go/slack2020/07/18 13:56:31 websocket_managed_conn.go:177: Connecting to RTM
slack-go/slack2020/07/18 13:56:32 rtm.go:71: Using URL:
slack-go/slack2020/07/18 13:56:32 websocket_managed_conn.go:181: Failed to start or connect to RTM: not_allowed_token_type
slack-go/slack2020/07/18 13:56:32 websocket_managed_conn.go:147: reconnection 1 failed: not_allowed_token_type reconnecting in 100ms
...

It is possible to still create apps that use the old permissions scopes but they are pushing everything to the events API.

More info in this thread slackapi/node-slack-sdk#921 (comment)

[shomali11]

Interesting. We will have to look into this further and see how it affects slacker and what we need to do to support both cases.

[leetrout]

Interesting. We will have to look into this further and see how it affects slacker and what we need to do to support both cases.

I am happy to help out if you're willing to entertain supporting both APIs. You never know with various projects where they draw the line.

Would you entertain PRs or think you're going to do the work yourself?

[shomali11]

Absolutely! Some of the features here we suggested and/or created by awesome contributors!
I definitely think we need to support both APIs just in case somehow. The question is how to make it as easy and intuitive to the user of slacker

I did some research. At the time when nlopes started the go-slack project, there was only support for RTM and slacker was built on top of that (https://github.com/slack-go/slack/blob/master/examples/websocket/websocket.go)

It seems that go-slack now supports an Events API as seen here (https://github.com/slack-go/slack/blob/master/examples/eventsapi/events.go). I wonder if we can leverage this somehow.

[leetrout]

Yeah, it looks like there is a relatively straightforward path to combine the command definitions with the events as they show up. I'm excited because this will let it run in lambda / cloud functions, too 😎

[cameronbrill]

Checking to see if you guys are wanting to work on adding support to Events API. If so, I want to help out as well.

[shomali11]

@cameronbrill Create a PR! Any help is very much appreciated

[arusso]

With the introduction of Socket-Mode communication protocol and support for it being added to upstream in slack-go, I think that means we have all the pieces needed to use the Events API via Sockets-Mode without having to re-architect your app to listen for calls from Slack on a public http endpoint.

[shomali11]

Awesome! Can you put a PR together?

[arusso]

Anything coming from me will take a while, as I am encumbered by policy and need to get approvals from my employer before I can contribute anything.

[paulkarayan]

Do you want a PR for updating the Readme? would have saved me an hour today :)
of course - Slacker is going to save me many hours now... all is good. Let me know!

[tvhung83]

I hope you can update README, and/or log out fatal errors. It took me hours to figure out that it only supports legacy bot token (by enabling DEBUG mode).