-
Notifications
You must be signed in to change notification settings - Fork 5
/
03_get_tweeters_examples.qmd
65 lines (43 loc) · 1.24 KB
/
03_get_tweeters_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
---
title: "Using APIs"
subtitle: "SICSS, 2022"
author: Christopher Barrie
format:
revealjs:
chalkboard: true
editor: visual
---
## Introduction
- Why get tweet*ers*?
- Get network characteristics
- Get user demographics
- Linked survey designs
## Introduction
- Why get tweet*ers*?
- Get network characteristics
- **Get user demographics**
- Linked survey designs
## Getting tweeters example
- As alternative to survey: <https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0259972>
![](images/geolocwm.png)\
## Geolocating
![](images/geolocwm2.png)\
## Getting ideology
- Using `tweetscores`
![](images/wmfol.png)\
## Getting demographics
- Using `M3` algorithm
<https://github.com/euagendas/m3inference>
## Comparing to ground truth
![](images/ideowm.png)\
## Limitations
- Measurement (estimation) error
- Bias...?
- Offline versus online populations
- Geolocation bias (?)
- Other applications...?
## Group work
1. Come up with a question answerable using `get_user_followers()` or `get_user_following()`
2. Formulate code needed to request that data
3. (If access granted) make the API call to get data
4. Consider limitations + design considerations