The part that says it will identify where the node twitter files are comes back with nothing.
I am in this loop of roadblocks.
Node-red is running on a Raspberry Pi.
I have done all platform updates and installed NPM.
The Twitter node is part of the original Raspian node-red. It shows in NPM as being installed, it also shows an upgrade available but the upgrade fails and reports as above.
The only other option is to disable. There is no option to delete.
I think there are many aspects of Node-RED that are great, but it seems that when something goes wrong and is not handled by the GUI the back end of things is a rats nest.
You are still on the very old version of nodejs. If you run the update script from the docs it will update that, but also move the twitter node to a place where you can then upgrade it.
You’re welcome. Apt should have updated node.js ( if you are on Stretch version of Raspbian) but it wouldn’t tidy up the nodes. Which is what you needed in order to upgrade Twitter easily.
Hi,
Regarding the changes in the Twitter API, If the tweet is longer than 160 characters the twitter input node returns a truncated msg.tweet.text and msg.tweet.truncated is true.
Just a few tweets includes an extended_tweet object with the full text and entities.
Could you update the node and include the extended param to get the full tweet by default?
In the other hand, receiving your direct messages option is broken, you don't receive any DMs.
I'm getting Error: HTTP Error 403: Forbidden, If I change or revoke the permissions I get Error: HTTP Error 401: Unauthorized, So I don't think is a permission issue, any idea?
btw, I can send DM's and get public content.
Sounds as if you still have the Access Tokens in place that don't include the Access Direct Messages option.
On the "Keys and Access Tokens" tab, Under "Your Access Token" check the Access Level thats selected and that these are the Tokens and Secret that you have used.
The Access Token and Access Token Secret change dependant on the options selected.
Part of the power of the Twitter API and being provisioned with a developer account - is the ability to provide twitter functionality to other users who do not have developer status. Previously functionality was granted by this node to access user accounts through the central twitter developer api access. It was easy to provision use by simple Oauth.
Can we get some insight into how node-red developers can utilize this functionality and create added value for twitter users who authorize this?