{"id":6788,"date":"2017-10-22T13:11:09","date_gmt":"2017-10-22T18:11:09","guid":{"rendered":"https:\/\/rud.is\/b\/?p=6788"},"modified":"2018-03-10T07:54:16","modified_gmt":"2018-03-10T12:54:16","slug":"a-call-to-tweets-blog-posts","status":"publish","type":"post","link":"https:\/\/rud.is\/b\/2017\/10\/22\/a-call-to-tweets-blog-posts\/","title":{"rendered":"A Call to Tweets (& Blog Posts)!"},"content":{"rendered":"

Way back in July of 2009, the first version of the twitteR<\/code> package was published by Geoff Jentry<\/a> in CRAN. Since then it has seen 28 updates, finally breaking the 0.x.y barrier into 1.x.y territory in March of 2013 and receiving it’s last update in July of 2015.<\/p>\n

For a very long time, the twitteR<\/code> package was the way<\/em> to siphon precious nuggets of 140 character data from that platform and is the top hit when one searches for r twitter package<\/code><\/a>. It even ha[sd] it’s own mailing list<\/a> and is quite popular, judging by RStudio’s CRAN logs total downloads stats \"\".<\/p>\n

I blog today to suggest there is a better way to work with Twitter data from R, especially if your central use-case is searching Twitter and mining tweet data. This new way is rtweet<\/code><\/a> by Michael Kearney<\/a>. It popped up on the scene back in August of 2016 and receives quite a bit of ? from the developer, especially on GitHub<\/a>.<\/p>\n

This post is short and mostly designed to convince you to (a) try out the package and (b) blog and tweet about the package — if you do agree that it’s the best modern way to work with Twitter from R — to raise awareness about it. Because of that focus, I won’t be delving into all of rtweet<\/code>‘s seekrits, but you can explore them yourself on it’s spiffy pkgdown site<\/a>.<\/p>\n

While both packages have nigh complete access to the Twitter API, I posit that the quintessential use-case for working with Twitter in R is searching through tweets\/users and then performing various types of data mining on the retrieved results. To that end, I’m going to show one use-case (out of many potential ones) that will both save you API-time and post-API munging time in order to convince you to switch to rtweet<\/code> and spread the word about it.<\/p>\n

Data-mining 300 #rstats<\/code> Tweets : A Play in Two Acts<\/h3>\n

We’ll search Twitter for #rstats<\/code>-tagged tweets with both twitteR<\/code> and rtweet<\/code>, starting with the former:<\/p>\n

library(twitteR)\r\n\r\n# this relies on you setting up an app in apps.twitter.com\r\nsetup_twitter_oauth(\r\n  consumer_key = Sys.getenv("TWITTER_CONSUMER_KEY"), \r\n  consumer_secret = Sys.getenv("TWITTER_CONSUMER_SECRET")\r\n)\r\n\r\nr_folks <- searchTwitter("#rstats", n=300)\r\n\r\nstr(r_folks, 1)\r\n## List of 300\r\n##  $ :Reference class 'status' [package "twitteR"] with 17 fields\r\n##   ..and 53 methods, of which 39 are  possibly relevant\r\n##  $ :Reference class 'status' [package "twitteR"] with 17 fields\r\n##   ..and 53 methods, of which 39 are  possibly relevant\r\n##  $ :Reference class 'status' [package "twitteR"] with 17 fields\r\n##   ..and 53 methods, of which 39 are  possibly relevant\r\n\r\nstr(r_folks[1])\r\n## List of 1\r\n##  $ :Reference class 'status' [package "twitteR"] with 17 fields\r\n##   ..$ text         : chr "RT @historying: Wow. This is an enormously helpful tutorial by @vivalosburros for anyone interested in mapping "| __truncated__\r\n##   ..$ favorited    : logi FALSE\r\n##   ..$ favoriteCount: num 0\r\n##   ..$ replyToSN    : chr(0) \r\n##   ..$ created      : POSIXct[1:1], format: "2017-10-22 17:18:31"\r\n##   ..$ truncated    : logi FALSE\r\n##   ..$ replyToSID   : chr(0) \r\n##   ..$ id           : chr "922150185916157952"\r\n##   ..$ replyToUID   : chr(0) \r\n##   ..$ statusSource : chr "<a href=\\"http:\/\/twitter.com\/download\/android\\" rel=\\"nofollow\\">Twitter for Android<\/a>"\r\n##   ..$ screenName   : chr "jasonrhody"\r\n##   ..$ retweetCount : num 3\r\n##   ..$ isRetweet    : logi TRUE\r\n##   ..$ retweeted    : logi FALSE\r\n##   ..$ longitude    : chr(0) \r\n##   ..$ latitude     : chr(0) \r\n##   ..$ urls         :'data.frame': 0 obs. of  4 variables:\r\n##   .. ..$ url         : chr(0) \r\n##   .. ..$ expanded_url: chr(0) \r\n##   .. ..$ dispaly_url : chr(0) \r\n##   .. ..$ indices     : num(0) \r\n##   ..and 53 methods, of which 39 are  possibly relevant:\r\n##   ..  getCreated, getFavoriteCount, getFavorited, getId, getIsRetweet, getLatitude, getLongitude, getReplyToSID,\r\n##   ..  getReplyToSN, getReplyToUID, getRetweetCount, getRetweeted, getRetweeters, getRetweets, getScreenName,\r\n##   ..  getStatusSource, getText, getTruncated, getUrls, initialize, setCreated, setFavoriteCount, setFavorited, setId,\r\n##   ..  setIsRetweet, setLatitude, setLongitude, setReplyToSID, setReplyToSN, setReplyToUID, setRetweetCount,\r\n##   ..  setRetweeted, setScreenName, setStatusSource, setText, setTruncated, setUrls, toDataFrame, toDataFrame#twitterObj<\/code><\/pre>\n
Both packages follow the similar idioms and you need to have done some prep-work by creating a Twitter “app” (both packages have instructions for that).<\/p>\n
That operation took about 3 seconds on a fast internet connection and wicked fast computer. What you get back is definitely usable data, but it’s in lists of custom objects. This is due to the way that package models the Twitter API on to custom R objects. It’s elegant, but also likely overkill for most operations. You can use something like purrr::map_df(r_folks, as.data.frame)<\/code> to get that list into a data frame, there are some other “gotchas”, such as text encoding (on a later run of this code both dplyr::glimpse()<\/code> and str()<\/code> gave me “invalid multibyte string”<\/em> errors but that same thing did not happen with rtweet<\/code>.<\/p>\n
Here’s the rtweet<\/code> version:<\/p>\n
library(rtweet)\r\n\r\n# this relies on you setting up an app in apps.twitter.com\r\ncreate_token(\r\n  app = Sys.getenv("TWITTER_APP"),\r\n  consumer_key = Sys.getenv("TWITTER_CONSUMER_KEY"), \r\n  consumer_secret = Sys.getenv("TWITTER_CONSUMER_SECRET")\r\n) -> twitter_token\r\n\r\nsaveRDS(twitter_token, "~\/.rtweet-oauth.rds")\r\n\r\n# ideally put this in ~\/.Renviron\r\nSys.setenv(TWITTER_PAT=path.expand("~\/.rtweet-oauth.rds"))\r\n\r\nrtweet_folks <- search_tweets("#rstats", n=300)\r\n\r\ndplyr::glimpse(rtweet_folks)\r\n## Observations: 300\r\n## Variables: 35\r\n## $ screen_name                    <chr> "AndySugs", "jsbreker", "__rahulgupta__", "AndySugs", "jasonrhody", "sibanjan...\r\n## $ user_id                        <chr> "230403822", "703927710", "752359265394909184", "230403822", "14184263", "863...\r\n## $ created_at                     <dttm> 2017-10-22 17:23:13, 2017-10-22 17:19:48, 2017-10-22 17:19:39, 2017-10-22 17...\r\n## $ status_id                      <chr> "922151366767906819", "922150507745079297", "922150470382125057", "9221504090...\r\n## $ text                           <chr> "RT:  (Rbloggers)Markets Performance after Election: Day 239  https:\/\/t.co\/D1...\r\n## $ retweet_count                  <int> 0, 0, 9, 0, 3, 1, 1, 57, 57, 103, 10, 10, 0, 0, 0, 34, 0, 0, 642, 34, 1, 1, 1...\r\n## $ favorite_count                 <int> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0,...\r\n## $ is_quote_status                <lgl> FALSE, FALSE, FALSE, FALSE, FALSE, FALSE, FALSE, FALSE, FALSE, FALSE, FALSE, ...\r\n## $ quote_status_id                <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ is_retweet                     <lgl> FALSE, FALSE, TRUE, FALSE, TRUE, TRUE, FALSE, TRUE, TRUE, TRUE, TRUE, TRUE, F...\r\n## $ retweet_status_id              <chr> NA, NA, "922085241493360642", NA, "921782329936408576", "922149318550843393",...\r\n## $ in_reply_to_status_status_id   <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ in_reply_to_status_user_id     <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ in_reply_to_status_screen_name <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ lang                           <chr> "en", "en", "en", "en", "en", "en", "en", "en", "en", "en", "en", "en", "ro",...\r\n## $ source                         <chr> "IFTTT", "Twitter for iPhone", "GaggleAMP", "IFTTT", "Twitter for Android", "...\r\n## $ media_id                       <chr> NA, "922150500237062144", NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, "92...\r\n## $ media_url                      <chr> NA, "http:\/\/pbs.twimg.com\/media\/DMwi_oQUMAAdx5A.jpg", NA, NA, NA, NA, NA, NA,...\r\n## $ media_url_expanded             <chr> NA, "https:\/\/twitter.com\/jsbreker\/status\/922150507745079297\/photo\/1", NA, NA,...\r\n## $ urls                           <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ urls_display                   <chr> "ift.tt\/2xe1xrR", NA, NA, "ift.tt\/2xe1xrR", NA, "bit.ly\/2yAAL0M", "bit.ly\/2yA...\r\n## $ urls_expanded                  <chr> "http:\/\/ift.tt\/2xe1xrR", NA, NA, "http:\/\/ift.tt\/2xe1xrR", NA, "http:\/\/bit.ly\/...\r\n## $ mentions_screen_name           <chr> NA, NA, "DataRobot", NA, "historying vivalosburros", "NoorDinTech ikashnitsky...\r\n## $ mentions_user_id               <chr> NA, NA, "622519917", NA, "18521423 304837258", "2511247075 739773414316118017...\r\n## $ symbols                        <lgl> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ hashtags                       <chr> "rstats DataScience", "Rstats ACSmtg", "rstats", "rstats DataScience", "rstat...\r\n## $ coordinates                    <lgl> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ place_id                       <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ place_type                     <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ place_name                     <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ place_full_name                <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ country_code                   <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ country                        <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ bounding_box_coordinates       <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...\r\n## $ bounding_box_type              <chr> NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, N...<\/code><\/pre>\n
That took about 1.5 seconds and provides a tidy, immediately usable data structure.<\/p>\n
\"\"<\/a><\/p>\n
But, that’s not all!<\/h3>\n
Michael has support for accessing the Twitter streaming API and also has some handy plot functions for quickly exploring retrieved Twitter content, enabling you to make pretty spiffy plots like this with almost<\/em> no effort (this was pirated from Michael’s package website):<\/p>\n
\"\"<\/p>\n
Fin<\/h3>\n
If the legacy twitteR<\/code> package is already in your workflows, there may be little to gain. But, I would suggest that R folks give rtweet<\/code> a try and blog about your experiences. It’ll give others a chance to see usage in different contacts and will also help spread the word about this alternative package and help bump up it’s pagerank.<\/p>\n
As I said on Twitter:<\/p>\n
\n
rtweet is to Twitter+R as dplyr is to databases+R: the best modern way to access the data\/API<\/p>\n
— boB Rudis (@hrbrmstr) October 22, 2017<\/a><\/p><\/blockquote>\n