summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authort <t@tjp.lol>2026-07-12 10:28:42 -0600
committert <t@tjp.lol>2026-07-12 10:28:50 -0600
commit92bd4424db18b10ec28653ba6c20efe22ef1637b (patch)
tree67090a43dc5dd9fa2fbb75e4a0465931e89f2f8b
parentd6ae35f4642c8f21649192d298ee3de9d553d163 (diff)
missed some formatting in an old post
-rw-r--r--weblog/gopher-item-types-a-gemini-miss.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/weblog/gopher-item-types-a-gemini-miss.md b/weblog/gopher-item-types-a-gemini-miss.md
index 4f76e2f..74aae4f 100644
--- a/weblog/gopher-item-types-a-gemini-miss.md
+++ b/weblog/gopher-item-types-a-gemini-miss.md
@@ -6,11 +6,11 @@ post_date: 2023-09-04
Hardly new, I know - a geminaut questions a design decision in the protocol.
-I came to the small web a little backwards. I discovered Gemini via the tildeverse a little over a year ago, quickly created this ~/public_gemini directory and got posting, responding to others' posts, and finding their responses on [Cosmos](gemini://skyjake.fi/~Cosmos/index.gmi).
+I came to the small web a little backwards. I discovered Gemini via the tildeverse a little over a year ago, quickly created this `~/public_gemini` directory and got posting, responding to others' posts, and finding their responses on [Cosmos](gemini://skyjake.fi/~Cosmos/index.gmi).
It was only after reading about [Gemini's philosophy and creation back-story](gemini://gemini.circumlunar.space/history/) that I started to learn about Gopher more deeply. Now, having written a few Gemini and Gopher servers and spent some time in both protocols, I question one design choice in Gemini being strictly _more powerful_ than gopher: the lack of anything performing the role of item types.
-Don't get me wrong: gopher's item types are a pain for implementors and a source of confusion for the unintiated ("what's with that magical /1/... path prefix?"). They certainly don't pass muster as a modern, simple, clean design. BUT one of the real joys of navigating around is the little indicators you get of what you're about to get yourself into with a link:
+Don't get me wrong: gopher's item types are a pain for implementors and a source of confusion for the unintiated ("what's with that magical `/1/` path prefix?"). They certainly don't pass muster as a modern, simple, clean design. BUT one of the real joys of navigating around is the little indicators you get of what you're about to get yourself into with a link:
```Sample output from gopher.floodgap.com as rendered in Bombadillo
--- Getting started with Gopher -------------------------------