node-red / node-red/node-red-nodes
Plan for upcoming Twitter API deprecation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
Twitter have now confirmed a date for when some of their deprecated APIs will be turned off. We need to get the Twitter node updated as soon as possible to minimise the disruption this will bring.
Most of the functionality is still available, but not all...
Twitter In
- the public stream for tweets containing the configured search term
- uses https://stream.twitter.com/1.1/status/filter
- no change needed
- all the tweets from accounts that the authenticated user follows
- uses deprecated https://userstream.twitter.com/1.1/user.json
- migrate to https://api.twitter.com/1.1/statuses/home_timeline.json - polled once a minute
- all tweets by specified users
- https://api.twitter.com/1.1/statuses/user_timeline.json
- no change needed
- direct messages received by the authenticated user
- uses deprecated https://api.twitter.com/1.1/direct_messages.json
- migrate to https://api.twitter.com/1.1/direct_messages/events/list.json - polled once a minute
- twitter events for the authenticated user
- uses deprecated https://userstream.twitter.com/1.1/user.json
- No viable alternative. The AccountActivity API relies on WebHooks - which we cannot use in non-public-cloud environments.
Twitter Out
- post status
- uses https://api.twitter.com/1.1/statuses/update.json
- no change needed
- post status with image attached
- uses deprecated https://api.twitter.com/1.1/statuses/update_with_media.json
- Follow migration guide - upload media first then use
/statuses/updateto tweet
- post new direct message
- uses deprecated https://api.twitter.com/1.1/direct_messages/new
- Migrate to https://api.twitter.com/1.1/direct_messages/events/new.json
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the Twitter In and Twitter Out operations listed in the issue and compare their deprecated endpoints with the proposed replacements. Verify the migration requirements for home timeline, direct-message events, and media uploads, while noting that authenticated-user events have no viable alternative. Done means the supported operations no longer depend on the listed deprecated endpoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100