summaryrefslogtreecommitdiff
path: root/content/entry/journal-update-022.md
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2023-04-09 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2023-04-09 00:00:00 +0000
commitd3ed44284015b55f9719e437ba1136575b3054734e52698c883c532cfc67bf22 (patch)
treeb67b6ba7a4a9c39110ad2b23d9fd2aa059990a2295971f8df9ec353fa07a422a /content/entry/journal-update-022.md
parente31ee953851614b5c981c313809fef2057a6569e3e206b39b44c0b67b6f755af (diff)
downloadjournal-d3ed44284015b55f9719e437ba1136575b3054734e52698c883c532cfc67bf22.tar.gz
journal-d3ed44284015b55f9719e437ba1136575b3054734e52698c883c532cfc67bf22.zip
Revert "Add URL fragments to URIs"
The Gemini specification does not say what Gemini clients/servers should do with URI fragments. Reference: https://gitlab.com/gemini-specification/gemini-text/-/issues/3
Diffstat (limited to 'content/entry/journal-update-022.md')
-rw-r--r--content/entry/journal-update-022.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/entry/journal-update-022.md b/content/entry/journal-update-022.md
index 8cfb4ab..230d039 100644
--- a/content/entry/journal-update-022.md
+++ b/content/entry/journal-update-022.md
@@ -9,7 +9,7 @@ In [my last journal entry update](/2022/09/19/journal-update-021/) back in Septe
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](/glossary/#digital-tulips) 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](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.