In the Twitter API there is a status_lookup method that "hydrates" a tweet. The docs are unclear about what this means. So when do I need to hydrate a tweet?
If I have tweets from /statuses/user_timeline
why would I need to hydrate them?
Please provide an example before and after of normal tweet and hydrated tweet and explain the difference.
From our Dataverse, you can download a list of tweet IDs and send them up to Twitter's live site to retrieve full tweets which you can then analyze. This automated action is called “rehydration”. Tweets can be “rehydrated” using a relatively simple computer program with a graphical user interface.
You just have to grant permissions to the Hydrator app to get a PIN. Enter this PIN in the app and you're all set to start hydrating your tweet IDs dataset (see images below for details). Next, you'll have to click on the “Add” tab in the app and select your tweet ids dataset.
Twitter IDs. Each object within Twitter - a Tweet, Direct Message, User, List, and so on - has a unique ID. At the very beginning of the platform, these IDs were small enough numbers that they could be generated sequentially. Over time, to accommodate growth, the IDs moved from being 32-bit, to 64-bit.
From the docs: "This method is especially useful to get the details (hydrate) a collection of Tweet IDs."
HYDRATE = get complete details (i.e. fields) of a tweet.
Many Twitter API calls that return tweets do not return all the fields. So, statuses/lookup
may be used as a secondary call to get these fields.
For example, search/tweets
may return tweets that have embedded video, but it will not return the URL of the embedded video. So, a second call to statuses/lookup
is required to get the video.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With