From 0e602cfa7881f789c3e9f1d5f25db9a8179cd0fc Mon Sep 17 00:00:00 2001 From: t Date: Sun, 12 Jul 2026 20:00:15 -0600 Subject: site updates --- weblog/gopher-item-types-a-gemini-miss.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'weblog/gopher-item-types-a-gemini-miss.md') diff --git a/weblog/gopher-item-types-a-gemini-miss.md b/weblog/gopher-item-types-a-gemini-miss.md index 74aae4f..dd0621e 100644 --- a/weblog/gopher-item-types-a-gemini-miss.md +++ b/weblog/gopher-item-types-a-gemini-miss.md @@ -2,6 +2,8 @@ post_date: 2023-09-04 --- +> Note: This was ported from my old gemini capsule, still served on gemini at `gemini.ctrl-c.club/~tjp` + # Gopher item types: A Gemini miss? Hardly new, I know - a geminaut questions a design decision in the protocol. @@ -33,5 +35,3 @@ MAP [6] Other Gopher clients for various platforms Will this link take me to another gopher menu? Show me a text file? Render an image? Download a binary file? Bounce me over to WWW? It's rather fantastic to get the visual cues that clients provide, and that's made possible by the information being embedded in the link itself in the underlying protocol. I miss that clarity when browsing gemini. - -> Note: This was ported from my old gemini capsule, still served on gemini at `gemini.ctrl-c.club/~tjp` -- cgit v1.3