Most of the changes don’t come in to effect until August, but one set of changes are being made with only 30 days notice. And as we’re only just become aware of them, we only have 20 days left to respond.
Unfortunately, the change that is coming in 20 days time is the most disruptive - it will prevent the existing Twitter node from signing in to the API and prevent it from working.
We will be working on a fix - but it will be a disruptive change to the node. When we publish the new version of the Twitter node and announce it here, not only will you have to update the node module, but you’ll also have to take additional steps to authenticate your twitter nodes.
I apologise for the inconvenience this will bring. This is a reality of maintaining nodes for other people’s APIs.