|
@@ -351,7 +351,7 @@ using wrong variables.
|
351
|
351
|
Additionally, we still need to split up the `twitter_timedate` variable, which
|
352
|
352
|
currently contains the point of time of the tweet in the form of
|
353
|
353
|
`YYYY-MM-DD HH:MM:SS`. For this, we again use regex and the function `sub()`.
|
354
|
|
-As `sub()` only replanes the first instance of the pattern given to it, if we
|
|
354
|
+As `sub()` only replaces the first instance of the pattern given to it, if we
|
355
|
355
|
have multiple occasions of a given pattern, we need to use `gsub()` (for global
|
356
|
356
|
substitute).
|
357
|
357
|
|
|
@@ -471,14 +471,14 @@ want much more than only the last 40, so we need to make several API-calls,
|
471
|
471
|
specifying the *"range"*. This is set with the `max_id=` parameter within the
|
472
|
472
|
URL. The "ID" is the
|
473
|
473
|
[unique identifier of each status/post](https://github.com/tootsuite/documentation/blob/461a17603504811b786084176c65f31ae405802d/Using-the-API/API.md#status).
|
474
|
|
-You can have several parameters with dividing them them the `&` character, which
|
|
474
|
+You can have several parameters in the query string by dividing them by the `&` character, which
|
475
|
475
|
will look similar to this:
|
476
|
476
|
```
|
477
|
477
|
https://DOMAIN.OF.INSTANCE/api/v1/timeline/tag/SEARCHTERM/?limit=40&max_id=IDNUMBER
|
478
|
478
|
```
|
479
|
479
|
|
480
|
|
-Luckily, we do not have to find out the ID manually. The header of the API
|
481
|
|
-response saved into the `mastodon_reqres` variable also lists the "*next page*"
|
|
480
|
+Luckily, we do not have to find out the ID manually. The header `link` of the API
|
|
481
|
+response is saved into the `mastodon_lheader` variable, it lists the "*next page*"
|
482
|
482
|
of results, so we can simply grab this with the `parse_headers()` function from
|
483
|
483
|
the `curl` package and use some regex to strip it out:
|
484
|
484
|
```
|