forked from cjbarrie/sicss_22
-
Notifications
You must be signed in to change notification settings - Fork 0
/
02_get_tweets_examples.qmd
67 lines (42 loc) · 1.24 KB
/
02_get_tweets_examples.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
---
title: "Using APIs"
subtitle: "SICSS, 2022"
author: Christopher Barrie
format:
revealjs:
chalkboard: true
editor: visual
---
## Introduction
- Why get tweets?
- Testing API call (again...)
- We can investigate text beyond keywords
- We can investigate additional tweet characteristics (metrics, annotations)
- We can investigate user characteristics...
## Getting tweets
- As barometer of public opinion
\
## Getting tweets
- As barometer of public opinion
- Coverage?
## Getting tweets
- As barometer of public opinion
- Bias?
{width="675"}\
## Getting tweets
- As barometer of public opinion
- Advantages versus surveys?
- Real-time ("always on")
- More accurately/realistically measured (?)
{width="589"}\
## Sampling tweets
- By keyword
## Geolocating tweets
- By user-reported location
## Group work
1. Replicate Flores (2017) using `get_all_tweets()` and another event of interest
2. Formulate code needed to request that data
3. (If access granted) make the API call to get data
4. Consider limitations + design considerations