rtm.start API method JSON response change

[bkomuves]

Starting from 2022 September 20, the Slack rtm.start API method's response will change (a lot of information is removed). See for example https://api.slack.com/changelog/2021-10-rtm-start-to-stop.

Looking at the source code, this will completely break this library, as it tries to parse back all the removed information into the data type SlackSession.

I'm not sure if this library is actively maintained, so the first question is, are you planning to do anything about this? Apparently the whole RTM API is deprecated, but I'm not sure what exactly that means in practice...

Thanks.

[velveteer]

Hey @bkomuves, I don't maintain this library but if you decide to make the switch from RTM to Socket Mode then I can recommend looking at https://github.com/velveteer/slacker. Otherwise I'd probably advise forking this repo to fix the breaking RTM changes yourself.

[bkomuves]

@velveteer Thanks for the answer!

After looking at it a bit more, I will probably switch to Socket Mode. Thanks for the library rec, it was not on Hackage so I haven't found it myself.

I want to invest a minimal amount of effort, as making our old bot working is not a high priority but would be nice; and fixing this library looks more work than I would like to invest. Your library looks a better choice, otherwise I was thinking just gluing say the Python SDK provided by Slack to the existing bot via some interprocess communication hack. But your lib looks the easiest way.