wezm/wezm.net
1
0
Fork 1
mirror of https://github.com/wezm/wezm.net.git synced 2024-11-10 01:42:32 +00:00
Code Issues Projects Releases Packages Wiki Activity

Fix some typos in turning-one-hundred-tweets-into-a-blog-post.md

Browse source
This commit is contained in:
Wesley Moore 2021-10-01 09:20:30 +10:00
parent 0d3db0c69d
commit 8bd50ce5af
No known key found for this signature in database
GPG key ID: BF67766C0BC2D0EE
1 changed files with 11 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
v2/content/posts/2020/turning-one-hundred-tweets-into-a-blog-post.md
View file

@ -3,20 +3,19 @@ title = "Turning One Hundred Tweets Into a Blog Post"
date = 2020-11-03T11:40:00+11:00 date = 2020-11-03T11:40:00+11:00
[extra] [extra]
#updated = 2020-06-19T09:30:00+10:00 updated = 2021-09-30T09:14:36+10:00
+++ +++
Near the conclusion of my [#100binaries] Twitter series I started working on Near the conclusion of my [#100binaries] Twitter series I started working on
[the blog post that contained all the tweets](@/posts/2020/100-rust-binaries/index.md). [the blog post that contained all the tweets](@/posts/2020/100-rust-binaries/index.md).
It ended up posing a number of interesting challenges and design decisions, as It ended up posing a number of interesting challenges and design decisions, as
well as a couple of Rust binaries. Whilst I don't think the process was well as a couple of Rust binaries. Whilst I don't think the process was optimal
necessary optimal I thought I'd share the process to show my approach to I thought I'd share the process to show my approach to solving the problem.
solving the problem. Perhaps the tools used and approach taken is Perhaps the tools used and approach taken is interesting to others.
interesting to others.
<!-- more --> <!-- more -->
My initial plan was to use Twitter embeds. Given a tweet URL it's relatively My initial plan was to use Twitter embeds. Given a tweet URL it's fairly
easy to turn it into some HTML markup. By including Twitter's embed JavaScript easy to turn it into some HTML markup. By including Twitter's embed JavaScript
on the page the markup turns into rich Twitter embed. However there were a few on the page the markup turns into rich Twitter embed. However there were a few
things I didn't like about this option: things I didn't like about this option:
@ -29,7 +28,7 @@ things I didn't like about this option:
So I decided I'd render the content myself. I also decided that I'd host the So I decided I'd render the content myself. I also decided that I'd host the
original screenshots and videos instead of saving them from the tweets. This original screenshots and videos instead of saving them from the tweets. This
was relatively time consuming as they were across a couple of computers and was a little time consuming as they were across a couple of computers and
not named well but I found them all in the end. not named well but I found them all in the end.
To ensure the page wasn't enormous I used the [`loading="lazy"`][lazy-loading] To ensure the page wasn't enormous I used the [`loading="lazy"`][lazy-loading]
@ -60,10 +59,11 @@ copy(tweets.join("\n"))
and pasted the result into [tweets.txt] in Neovim. and pasted the result into [tweets.txt] in Neovim.
When all pages had be processed I turned the nitter.net URLs in to twitter.com URLs: When all pages had be processed I turned the nitter.net URLs back in to
`:%s/nitter\.net/twitter.com/`. twitter.com URLs: `:%s/nitter\.net/twitter.com/`.
This tells Neovim: for every line (`%`) substitute (`s`) `nitter.net` with `twitter.com`. This tells Neovim: for every line (`%`) substitute (`s`) `nitter.net` with
`twitter.com`.
### Turning Tweet URLs Into Tweet Content ### Turning Tweet URLs Into Tweet Content
@ -73,7 +73,7 @@ this (possibly via [twurl]) but that is not what I did. Onwards!
I used the unauthenticated [oEmbed API][oembed] to get some markup for each I used the unauthenticated [oEmbed API][oembed] to get some markup for each
tweet. `xargs` was used to take a line from `tweets.txt` and make the API tweet. `xargs` was used to take a line from `tweets.txt` and make the API
(HTTP) request with `curl`] (HTTP) request with `curl`:
``` ```
xargs -I '{url}' -a tweets.txt -n 1 curl https://api.twitter.com/1/statuses/oembed.json\?omit_script\=true\&dnt\=true\&lang\=en\&url\=\{url\} > tweets.json xargs -I '{url}' -a tweets.txt -n 1 curl https://api.twitter.com/1/statuses/oembed.json\?omit_script\=true\&dnt\=true\&lang\=en\&url\=\{url\} > tweets.json