https://api.twitter.com/2/tweets/search/all + something + something else
SICSS, 2022
Christopher Barrie
Counting tweets
Applied examples
Group work
Getting tweets
Applied examples
Group work
Extracts visible content from screen
Often trial and error as not optimized for serving data ( legibility not readability)
Requests content from a “blank” version of page
Delivers data in more readily usable format (JSON, csv etc.)
https://api.twitter.com/2/tweets/search/all + something + something else
my_query <- "#BLM lang:EN"
endpoint_url <- "https://api.twitter.com/2/tweets/search/all"
params <- list(
"query" = my_query,
"start_time" = "2021-01-01T00:00:00Z",
"end_time" = "2021-07-31T23:59:59Z",
"max_results" = 20
)
params
$query
[1] "#BLM lang:EN"
$start_time
[1] "2021-01-01T00:00:00Z"
$end_time
[1] "2021-07-31T23:59:59Z"
$max_results
[1] 20
[1] "https://api.twitter.com/2/tweets/search/all?query=%23BLM%20lang%3AEN&start_time=2021-01-01T00%3A00%3A00Z&end_time=2021-07-31T23%3A59%3A59Z&max_results=20"
academictwitteR
academictwitteR
Why?
Especially, since intro. of Academic Research Product Track…
Go here
Or a live example…
This is what the Developer Portal looks like
Don’t forget to Restart R
We’re good to go 🥳
We’re good to go 🥳…
Sort of
“I don’t think researchers should not be automatically bound by such terms-of-service agreements. Ideally, if researchers violate terms- of-service agreements, they should explain their decision openly… as suggested by transparency-based accountability. But this openness may expose researchers to added legal risk…”
““By employing TOS- compliant methods, you are respecting the business prerogatives of the company that created the platform you are studying, but you may or may not be respecting the dignity and privacy of the platform’s users” ”