-
-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
classic Apps and legacy custom bots deprecated after 4th June 2024 #513
Comments
That's correct, RTM for new bots is DOA. If you're writing a new bot today you should use events (e.g. https://github.com/slack-ruby/slack-ruby-bot-server-events and https://github.com/slack-ruby/slack-ruby-bot-server-events-app-mentions), and use this library for Web API (send messages, etc.). I wrote this about one migration and have more recently migrated https://github.com/dblock/slack-sup2 from https://github.com/dblock/slack-sup, the interesting change is dblock/slack-sup2@c7c761e. It's a ton of work for otherwise perfectly working applications. I have half a dozen, so I hate having to rework them. I am not happy Slack is removing support for RTM. |
@MarioRuiz it would be nice if someone (you?) could contribute updates to this project code / README about what's being removed/deprecated. |
Thanks for the response @dblock |
Yes, this is a basic message event (https://api.slack.com/events/message). |
It seems like I cannot use Events since my bot is an internal development so it is not opened to internet. They recommend to use Sockets for that https://api.slack.com/apis/connections/socket |
I do not. If someone/you wants to contribute support here that'd be great! |
I created a code that is working fine with Sockets, not much time to contribute though, I post it here if anyone want to use it
|
I just got an email from Slack informing that we won't be able to create new classic Slack apps or legacy custom bots, so I guess we will not be able to use RTM, am I correct? And if I understand correctly slack-ruby-client using events is not covering everything we can do with RTM, is there any expected way to solve this?
The text was updated successfully, but these errors were encountered: