node-red / node-red/node-red-nodes

Plan for upcoming Twitter API deprecation

Open
#443 8 comments 0 reactions 0 assignees View on GitHub

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
Twitter Out

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.