SlackAPI rtm.start depreciated starting 2022/09/20

It looks like the rtm.start API method is depreciated in september of 2022, and will start returning a shortened response identical to rtm.connect. Are there plans to update the SlackClient to move over to rtm.connect and handle the new truncated response?

May 10 '22 18:05 hartjac23

Hi,

maybe its just me, but I cannot get the /api/rtm.start method working at all. It requires the scope "rtm.stream" and I cannot add this scope to my user token?

Jun 01 '22 20:06 kanadagermane

It looks like this lib no longer works. Any chance of a hotfix?

Sep 28 '22 17:09 iclaxton

Also hoping for this ^ . Didn't realize it was using rtm.start (api changed yesterday) - but it indeed appears to.

Sep 28 '22 23:09 glenwperry

I'm not opposed to accepting a PR that would resolve this, but I don't personally have any reason to fix it. I've also got a lot of things happening in my personal life, so this library isn't a priority for me at this time.

Sep 30 '22 03:09 Inumedia

If you do not need the Slack Real Time Messaging API specifically, I'd suggest switching over to soxtoby/SlackNet.

Also:

1- You probably shouldn't be using a socket-based API if the Web API serves your purposes. 2- You probably should be using the new Socket Mode API if you really need to keep track of events through sockets.

Sep 30 '22 12:09 vedxyz

Hi @Inumedia, I totally understand and will help unless anyone else is already on it. Sending my best regards and thanks for all your work on this lib to date.

Sep 30 '22 14:09 iclaxton