At Source, Jacob Harris notes that, as appealing as the Twitter API may be as a source of what-people-are-thinking data, it’s hardly perfect. Twitter’s demographics aren’t representative of either Internet users as a whole or the broader population, and geocoding data is sparse and inconsistent.
“But what does Twitter think?”
If you are a data journalist in a newsroom, you will hear this question sooner or later in your career. It doesn’t really matter the context—I’ve heard it asked about everything from the Academy Awards to the Westminster Dog Show to presidential debates or the death of Osama bin Laden. And why not? It certainly sounds like a great idea. Twitter is such a conversational medium, it seems like an easy way to dip into the mindset of the world to see what they think. But as with all great ideas, it’s very easy to go wrong.
I’d add that different versions of Twitter data can return different — sometimes even mutually contradictory — results, as explored in this paper by Morstatter, Pfeffer, Liu, and Carley, which notes that the results generated by Twitter’s Streaming API (which provides only a sampled subset of all tweets) and the full (expensive) Twitter firehose:
The API service has been used by many researchers, companies, and governmental institutions that want to extract knowledge in accordance with a diverse array of questions pertaining to social media. The essential drawback of the Twitter API is the lack of documentation concerning what and how much data users get. This leads researchers to question whether the sampled data is a valid representation of the overall activity on Twitter. In this work we embark on answering this question by comparing data collected using Twitter’s sampled API service with data collected using the full, albeit costly, Firehose stream that includes every single published tweet. We compare both datasets using common statistical metrics as well as metrics that allow us to compare topics, networks, and locations of tweets. The results of our work will help researchers and practitioners understand the implications of using the Streaming API.
All that’s not to say that Twitter’s not incredibly useful as a data source — lord knows we like what it does for Fuego, and few tools can provide the slice of broader sentiment it does as quickly and easily. Just be aware of its limits and be careful about assuming what it produces represents any larger reality.
2 comments:
I think there’s a missing word in your first paragraph. Shouldn’t it be: “Twitter’s demographics are NOT representative of either Internet users as a
whole or the broader population, and geocoding data is sparse and
inconsistent.”
True! Fixed.
Trackbacks:
Leave a comment