moves blog posts to new position to be consistent with gemlog

2026-03-24 22:07:05 +00:00
parent 4b720b8dd7
commit 706f5913e6
30 changed files with 25 additions and 70 deletions
@@ -1,9 +1,11 @@
 ---
-title: How I read things on the Internet now (no, of course I don't leave the terminal!)
+title:
  How I read things on the Internet now (no, of course I don't leave the
  terminal!)
 description: >-
-  I've been sprucing up how I follow what's happening on the Internet. I can
+  I've been sprucing up how I follow what's happening on the Internet. I can now
-  now read all the things I want to read pretty efficiently, and enjoy doing
+  read all the things I want to read pretty efficiently, and enjoy doing it,
-  it, which is exciting.
+  which is exciting.
 pubDate: 2025-01-19
 ---
@@ -16,15 +18,14 @@ Some interesting people write blog posts. Some beautiful people make music. Some
 silly people make comedy sketches. Sometimes my friends are sharing stuff with
 their friends, which means me (WIP on that front: I'll get back to that).
-I want to know about it. I want to read interesting things that will educate
+I want to know about it. I want to read interesting things that will educate me.
-me. I want to hear beautiful music. I want to hear about what my friends are up
+I want to hear beautiful music. I want to hear about what my friends are up to.
 to.
 I can't read everything as it comes in, it's too much: I'll need to sift a lot
 of it out quickly. I'll need to sift through it regularly to stay on top of it:
 like, several times a week, if not daily. And sometimes, while I'm doing my
-daily sifting, I'll find something I really want to read, but I haven't got
+daily sifting, I'll find something I really want to read, but I haven't got time
-time right now: I'll save this for the weekend.
+right now: I'll save this for the weekend.
 For a while, I've been hosting [CommaFeed][commafeed] on [PikaPods][pikapods].
 This has been OK ([OMG, RSS is cool][rss]), but the interface is just clunky
@@ -32,15 +33,15 @@ enough to make it a chore to use. That means I don't sift through stuff
 regularly, and that means my feed piles hundreds of unread posts high.
 It also hasn't been any good for distinguishing between stuff I don't want to
-read *ever*, and stuff I don't want to read *right now* but will get round to
+read _ever_, and stuff I don't want to read _right now_ but will get round to
-later. I could in theory use the bookmarking feature built-in to my browser,
+later. I could in theory use the bookmarking feature built-in to my browser, but
-but removing things after I've read them is too clunky, so I don't do it.
+removing things after I've read them is too clunky, so I don't do it.
 ## The solution
 Every morning, I open my terminal and run [newsboat][newsboat].
-![newsboat showing how many unread posts I have at a glance in the opening view](./newsboat.webp)
+![newsboat showing how many unread posts I have at a glance in the opening view](./2025-01-19_newsboat.webp)
 I know the unread count is pretty fresh, because I've set up a systemd service
 to run newsboat at startup to fetch the feeds.
@@ -48,7 +49,7 @@ to run newsboat at startup to fetch the feeds.
 I press `l` twice to open a post. Then I press `n` to navigate to the next
 unread post until I run out of unread posts.
-![newsboat displaying a post](./newsboat-post.webp)
+![newsboat displaying a post](./2025-01-19_newsboat-post.webp)
 If I encounter something I want to read later, but don't have time right now, I
 press `b`, which runs a home-made bookmarking script. Here it is:
@@ -85,11 +86,11 @@ curl "$url" > "$HOME/readlist/unread/$filename"
 I can also run this script manually and pass it a URL of my choice at any time,
 say, if I find an interesting article while browsing the Web.
-When I want to read from my reading list, I run `readnow.sh`, which simply
+When I want to read from my reading list, I run `readnow.sh`, which simply opens
-opens my reading list folder, `~/readlist/unread`, in my terminal file browser
+my reading list folder, `~/readlist/unread`, in my terminal file browser of
-of choice: namely, [ranger][ranger].
+choice: namely, [ranger][ranger].
-![ranger showing the contents of my reading list with a preview](./ranger.webp)
+![ranger showing the contents of my reading list with a preview](./2025-01-19_ranger.webp)
 Although ranger has a preview, I'll typically open the file up in my terminal
 web browser of choice, which is [w3m][w3m] (plus a couple of custom
@@ -108,18 +109,18 @@ ext x?html?, ...
 ...
 ```
-Having configured my default web browser in my ranger config, all
+Having configured my default web browser in my ranger config, all I need to do
-I need to do is press `l`.
+is press `l`.
-![A post displaying in w3m](./w3m.webp)
+![A post displaying in w3m](./2025-01-19_w3m.webp)
 No ads, no cookie popups, no giant banner images taking 2 seconds to load and
 shifting the content all over the place: just the text I want to read. Isn't it
 beautiful?
 Once I'm finished reading the post, I'll press `q` to quit w3m and return to
-ranger. Assuming I don't need to read it again, I'll press `dm` to move the
+ranger. Assuming I don't need to read it again, I'll press `dm` to move the post
-post to `~/readlist/read` - my way of marking a post as 'read'.
+to `~/readlist/read` - my way of marking a post as 'read'.
 I've done this by writing a super simple script, `markread.sh`:
@@ -155,8 +156,7 @@ map dm shell markread.sh %f
 I can now keep up to date, and I enjoy doing it.
-I get not everyone likes to live in the terminal. I think the key takeaways
+I get not everyone likes to live in the terminal. I think the key takeaways are:
 are:
 - Make it really easy to sift through new posts
 - When you sift, sift through every post, and for each one, either read it
@@ -1,45 +0,0 @@
 ---
 title: The structure of Genesis
 pubDate: 2026-03-21
 description: I've been reading the Book of Genesis recently.
 ---
 Last night, I tried a favourite exercise of mine. It's very simple. I wrote down a list, in order, of all the 'episodes' in Genesis. That is, I wrote down a list that went:
 * Creation
 * Adam and Eve
 * Cain and Abel
 * Genealogy of Noah
 * Noah and the Flood
 * …
 …and so on, all the way to Joseph.
 Once I'd finished this, I was surprised at the result. I realised that, without consciously thinking it, I had been expecting to find a single, clear structure, and in particular, one that went: patriarch, genealogy, patriarch, genealogy, and so on. I didn't find that at all.
 For sure, patriarchs and genealogies are major structures in Genesis, and you'll get a long way thinking about Genesis as a story of six patriarchs and so many genealogies (though the genealogies are rather more difficult to count). Indeed, you *can*, if you really want, slice up Genesis into six neat patriarch cycles and glue them back together again with genealogies: Adam (1-5), Noah (5-11), Abram (11-25), Isaac (25-27), Jacob (27-36), Joseph (36-50). But this way of thinking cannot comprehensively account for the whole book.
 For one thing, there are a good few pieces in Genesis which are difficult to fit into a patriarch jigsaw. Why is there so much material about Cain, Hagar, Ishmael, Esau, and Dinah, including genealogies? Why is the Tower of Babel in there? If Genesis is all about the patriarchs, these are all lengthy side-alleys. (May I say pends? Closes?)
 For two things, this neat six-part series is more messy than it might at first appear. On this model, the genealogies function to glue together the patriarch narratives. Sometimes, this model works well: the genealogy in chapter 5 does a good job of connecting Adam to Noah, and the one in chapter 10 gets us from Noah to Abram. But from Abram to Jacob to Joseph, there's no need for genealogies to stitch things together, because we're only taking one step on the genealogical ladder at a time, from father to son to grandson.
 So, in chapter 25, instead of a 'genealogy' from Abram to his son Isaac, we get genealogies of Keturah and Esau: genealogical 'dead ends' from a patriarchal point of view. In chapter 36, where we're 'supposed' to be linking Jacob to his son Joseph, we get another genealogy of Esau. And in chapter 27, at the join between the supposed 'Isaac cycle' and the supposed 'Jacob cycle,' there's no genealogy at all.
 I'm not for a moment trying to tell you that this model is *useless* for understanding Genesis. Far from it! I don't think you can understand Genesis as a coherent whole without considering it as a story of six patriarchs. I'm just saying this model is *inadequate*. It seems that to account for the Book of Genesis, we're going to have to structure it in multiple ways. To me, that's wonderfully exciting.
 In particular, I'm considering all these to be worthwhile ways to look at Genesis as a whole:
 * Genealogies! (Without assuming they are centred on the six patriarchs!)
 * 'These are the generations of…' (how many occurrences can you find?)
 * Yahweh speaking to people! (Always one person alone: did you notice that?)
 * Wives! (How many can you think of? Will you include Potiphar's wife in this analysis? What about Dinah?)
 * Anti-patriarchs and foreigners! (Does Adam get as much column space as Abimelech, or Esau?)
 * Wells! (Some of them appear twice, or even thrice…)
 * Names and naming! (Do you remember why Jacob is called 'Jacob'?)
 * Deaths and burials! (How did Abraham end up buried in that cave?)
 None of these structural lenses is adequate for seeing the whole thing in focus. But each one adds a new dimension. They all pile on top of one another. It's difficult to think of a physical analogy, because in my experience, things don't tend to occupy the same physical space at the same time, and I don't want to resort to the 'kaleidoscope' cliché. I guess it's a bit like quantum super-position, but instead of something being both 'up' and 'down' at the same time, it's multiple Persian rugs. Each one has its own colour scheme, its own patterns, its own delicately balanced symmetries. And yet, just as each rug is intricately harmonious within itself, it is no less intricately arranged into complex symphony with every other rug. And yet, somehow, all the rugs are simultaneously woven out of the same yarn. Picture that!
 Of course, you can also read Genesis without attempting to comprehend the entire thing at once. You can also study a single episode, like the Tower of Babel, without trying to squeeze it into a grand narrative of the whole of Genesis. I suspect lots, if not all, of the stories in Genesis were originally told orally and independently of each other, and I think it's perfectly valid to read them independently once again.
 Nevertheless, the author or authors of Genesis, and, more importantly, the Holy Ghost who moved them, once decided that it would be a good idea to put these stories and genealogies in an orderly sequence in the same scroll, and deliberately and explicitly relate them to one another. By considering structural lenses, we're joining the human authors, and generations of readers, in the faith that these stories mean something to each other, that they have something to tell us not only independently but also together.