From 60e7722f301f2f87255dfba12aea8746d1501d5fa33a5f9bbb21cc5c8cf74856 Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Tue, 28 Jan 2025 00:00:00 +0000 Subject: New entry: journal-update-28 --- content/entry/journal-update-28.md | 40 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 content/entry/journal-update-28.md (limited to 'content/entry') diff --git a/content/entry/journal-update-28.md b/content/entry/journal-update-28.md new file mode 100644 index 0000000..a522192 --- /dev/null +++ b/content/entry/journal-update-28.md @@ -0,0 +1,40 @@ +--- +title: "Journal Update 28: Writing Less" +date: 2025-01-28T00:00:00Z +tags: ['journal updates'] +draft: false +--- +## What's New + + +### Writing Less + +> "I have no plans to abandon this journal. Once I’m achieving some of my big-picture goals, I’ll probably come back to continue writing." + +I wrote that in "[Taking a Step Back](/2023/12/09/journal-update-26/ "Journal Update 26: Taking a Step Back")". A year on, it seems naïve to have thought that I would return to writing at the same pace as before. I'm not sure if that's what I meant there, but that's how I interpret it now. Since then, I've worked toward some of my goals and endured unexpected life changes along the way, both of which have contributed to a newfound clarity on the general, near-term direction I want my life to go. + +Working toward that new direction, I don't expect to return to writing at the pace or intensity I used to any time soon, and maybe never. So I'm going to stop including entry forewords about how I haven't "returned to writing" yet, and just write whenever I have the extra time and energy. My time and energy are currently highly variable, so expect no further updates about how frequently I will write, as I don't want to explain every time circumstances change. + +If you don't want to read this whole entry, that was the important bit. You can go now or stay and read the boring maintenance. It's up to you. :) + + +### Maintenance + +* [Timestamped this journal](/2024/04/08/why-i-timestamped-my-journal/ "Journal Entry: Why I Timestamped My Journal") under the SHA-256 Git object format to replace the old timestamp which used broken SHA-1 +* Mirrored all my Git repositories on [Codeberg](https://codeberg.org/nicholasjohnson "Git Repositories Mirror") (SHA-2 repositories are *finally* supported now) +* Removed the promoted page (I may write about its listed topics later) +* Switched hosted files over to torrents + +For the sake of the cryptographic integrity of this journal, all my files I share here have either been included in the signed Git repository directly, or put into v2 torrents. I'd like to do something similar for external links but I'm not aware of a good way to accomplish that. + + +## Future Plans + +* Add more [tags](/tags/ "Journal Tags") +* Create autoconfiguration script for server (Gemini capsule, website, SimpleX, e-mail, Git, etc) + +In the past, I dismissed automating my server configuration as not worth the effort. My thoughts on that have since changed and I'd rather do that work upfront than risk something happening at an inopportune time and having to suddenly reconfigure everything manually. + +In my [previous journal update](/2024/07/04/journal-update-27/ "Journal Update 27: New Onions!"), I mentioned moving my Gemini and SimpleX server root certificates offline for compromise recovery. For that, I would need to periodically sign new online certificates. I can't fully automate that, but it makes a good argument in favor of automating the server configuration. With an automated server configuration, I could make processes like these as painless as possible, and so that they don't depend on the undocumented custom configuration of a specific server. + +I'd like to work on the automation for the server configuration and other server-related processes in the open, so I'll push that Git repository after I've built it. -- cgit v1.2.3