-
Notifications
You must be signed in to change notification settings - Fork 605
temporary solution for direct messages #415
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
Conversation
…ed for the pull request).
|
I corrected the code, I don't know how to solve the issue ? close this request and open a new one after a new commit ? |
|
Thanks @eRudy. If you push another commit, the PR will pick it up automatically. However, if this is still using the deprecated API, then it doesn't buy us much. The required work is to move to the new api once and for all. |
|
I understand, but should not the correction done in the twitter-ng library used by node-red ? |
2 similar comments
|
Thanks - As noted this is a short term fix... what we really need is to move to the new API |
Added a detection of the pattern "D < user > < message >" in order to use the specific function of the twitter-ng library to send direct messages (newDirectMessage).
Sadly it's only a temporary fix, since the API will be deprecated in June 19, 2018 (https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/guides/direct-message-migration)