-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
How much work should it be to update this very nice package with this in mind?
As we outlined in April, User Streams and Site Streams, along with the legacy Direct Message endpoints, will be replaced by improved products such as Account Activity API.
Today, we are providing notice that on June 19, 2018 we are retiring the following services and endpoints:
User Streams
Site Streams
GET direct_messages
GET direct_messages/sent
GET direct_messages/show
POST direct_messages/destroy
any application, code or script reliant on these endpoints, or consuming libraries that rely on these endpoints, WILL cease to function after this date, and we strongly encourage all app and library developers to update code and documentation accordingly to avoid negative user experiences after this time
Further detail is provided in this blog post.
Please see our two migration guides for further assistance:
Account Activity API migration guide (for User Streams and Site Streams developers)
Direct Message endpoints migration guide (for Direct Message developers)
We encourage developers to follow announcements here on the forums, and to watch the developer platform roadmap, as we continue to invest in the API platform and to make new features available.
Looking at the code it looks like it's working off either GET direct_messages or User Streams right? Doesn't look like the direct_messages/new is affected so responding should work into the future.
I'm starting to build a prototype on this with the soon to be killed endpoint. -- If this works out well using the older endpoint I'm happy to make the changes -- just wanting some guidance if the OP thinks it's a big deal to change.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels