diff options
Diffstat (limited to 'content/entry/journal-update-022.md')
| -rw-r--r-- | content/entry/journal-update-022.md | 25 |
1 files changed, 6 insertions, 19 deletions
diff --git a/content/entry/journal-update-022.md b/content/entry/journal-update-022.md index 81f1d4f..8e3b363 100644 --- a/content/entry/journal-update-022.md +++ b/content/entry/journal-update-022.md @@ -2,34 +2,21 @@ title: "Journal Update 022" date: 2022-12-04T00:00:01 draft: false -makerefs: false --- ## What's New -In my last journal entry update back in September[1], I talked about rebranding away from nicksphere to just my name, nicholasjohnson. Well I've finished the rebranding. For more on that, see my previous journal entry.[2] I accomplished it by the most straightforward way possible: setting up everything in parallel on a fresh server, then updating the domains. I changed some backend server stuff, but probably nobody cares about those details. +In [my last journal entry update](/2022/09/19/journal-update-021/) back in September, I talked about rebranding away from nicksphere to just my name, nicholasjohnson. Well I've finished the rebranding. For more on that, see [my previous journal entry](/2022/12/04/domain-change-announcement/). I accomplished it by the most straightforward way possible: setting up everything in parallel on a fresh server, then updating the domains. I changed some backend server stuff, but probably nobody cares about those details. Using Ansible, I automated configurations that remain the same across servers I use. At some point in the future when it's ready, I'll git push the playbook. I decided not to automate the entire server. For every change I make on the server, I'd have to update the Ansible scripts, creating twice the work. It would only save me time in the scenario where my server is wiped and I need to reprovision it from scratch. That situation is very rare, so automating isn't worth it. -My new VPS accepts many payment methods, so I don't depend on digital tulips[3] anymore. Unfortunately my VPS provider doesn't have IPv6 support yet, but I've been assured that they already have the IPv6 addresses and they're just working on assigning them now. +My new VPS accepts many payment methods, so I don't depend on [digital tulips](/glossary/) anymore. Unfortunately my VPS provider doesn't have IPv6 support yet, but I've been assured that they already have the IPv6 addresses and they're just working on assigning them now. -I decided to drop I2P support for the time being. It was broken anyways for who knows how long. If you want to know more about that, read this Git commit message[4]. If you use the Tor onion[5][6] to access this journal, nothing has changed. I migrated the onion to the new VPS as-is. +I decided to drop I2P support for the time being. It was broken anyways for who knows how long. If you want to know more about that, read this [Git commit message](https://git.nicholasjohnson.ch/journal/commit/?id=85b77079ffea8fae7f29516dc029812000c457fb). If you use the [Tor](gemini://nick6gsepvtmkcpibpid6dqtqroxt62u6ab4ep65vxrenffruumj6jad.onion) [onion](http://nick6gsepvtmkcpibpid6dqtqroxt62u6ab4ep65vxrenffruumj6jad.onion) to access this journal, nothing has changed. I migrated the onion to the new VPS as-is. In the journal repository, I've started signing Git tags rather than commits. Git-annex has been removed for cleaner code and better accessibility on Sourcehut. The ugly Python code has been entirely removed and replaced with two Hugo configuration files, meaning Hugo properly generates my journal now all on its own. I switched from emojis to using emoji codes for better code accessibility. -Finally, I archived my old repos on Sourcehut.[7] I didn't want them completely gone since they're linked to in some of my old entries and I try hard to avoid link rot, but I also didn't want them so front and center since they're poorly written. +Finally, I archived [my old repos on Sourcehut](https://sr.ht/~nicholasjohnson/archive/). I didn't want them completely gone since they're linked to in some of my old entries and I try hard to avoid link rot, but I also didn't want them so front and center since they're poorly written. ## Future Plans -For the Hugo theme for this journal, you can find my plans in this TODO file[8]. I'm going to start versioning the theme. Once I implement the features in the TODO file, as long as nothing else occurs to me, I'll make the first official release of the theme with version 1.0.0. +For the Hugo theme for this journal, you can find my plans in [this TODO file](https://git.nicholasjohnson.ch/hugo-theme-journal/tree/TODO?id=33f2df0c33830298bef1e35fc6dc49fe1df23c8e). I'm going to start versioning the theme. Once I implement the features in the TODO file, as long as nothing else occurs to me, I'll make the first official release of the theme with version 1.0.0. -As for the journal itself, eliminating the promoted links page[9] is the only major change I have planned and that will happen gradually. - - -Link(s): -[1: Journal Update 021](/2022/09/19/journal-update-021/) -[2: Domain Change Announcement](/2022/12/04/domain-change-announcement/) -[3: Glossary: Digital Tulips](/glossary/) -[4: Drop I2P Support](https://git.nicholasjohnson.ch/journal/commit/?id=85b77079ffea8fae7f29516dc029812000c457fb) -[5: Tor Onion Capsule](gemini://nick6gsepvtmkcpibpid6dqtqroxt62u6ab4ep65vxrenffruumj6jad.onion) -[6: Tor Onion Site](http://nick6gsepvtmkcpibpid6dqtqroxt62u6ab4ep65vxrenffruumj6jad.onion) -[7: Old Git Repos Archive](https://sr.ht/~nicholasjohnson/archive/) -[8: hugo-theme-journal TODO](https://git.nicholasjohnson.ch/hugo-theme-journal/tree/TODO?id=33f2df0c33830298bef1e35fc6dc49fe1df23c8e) -[9: Promoted Links](/promoted/) +As for the journal itself, eliminating the [promoted links page](/promoted/) is the only major change I have planned and that will happen gradually. |