Minor germinal update: link syntax So, the Gemini link syntax was finalized:
Link Syntax Finalized
The one place this affects Germinal is in the generation of directory indexes. Germinal’s directory indexing code has been updated accordingly.
I have also updated the links on my Gemini site.
Unless there are changes coming to the response header line format, this is probably the last Gemini change that actually affects Germinal. Pretty much everything else is client-side.
Is the gemini map format intended to be reflowed? One question that hasn’t been addressed in the Gemini speculative specification is whether the Gemini map file format text/gemini is intended to be reflowed. By reflowed, I mean mainly that the line-length of the file itself is not intended to be mapped exactly to the output device, which should instead lay out the text with appropriate line lengths. This is what HTML renderers do, and what MarkDown renderers do, usually by way of conversion to HTML.
Germinal is a server for the Gemini Protocol that I’ve been writing in Common Lisp during my lunches and some evenings.
It is named after the early 20th century Yiddish-language anarchist newspaper Germinal. I wanted to name it after an anarchist publication to convey the idea of people sharing information and ideas with each other, in contrast to the way the web is used to push advertising from corporations to people.
Good netizen solderpunk has been writing about the design of a protocol that is slightly more complex than gopher, but significantly simpler than http; while at the same time being significantly more powerful than gopher. I have thoughts about this, as I’ve posted about before, and I’m interested in contributing to this project and the conversation around it. These are the main documents where they discuss it. If you only have time for one, read just the FAQ, but they are all worthwhile and short, easy reads.
If you don’t have a gopher client handy, you can browse the gopherverse using the Floodgap Gopher-HTTP Gateway. It will proxy gopher pages to you over https, so you can read them in a browser that doesn’t support gopher. The OverbiteWX extension for Firefox uses it to handle gopher URLs.
This is a very useful service, but the design is not very appealing to me. Gopher is supposed to be simple plain text, it’s true.
As part of the ongoing revitalization of gopher, there has been quite a bit of discussion about what, exactly, is good about gopher, and whether you can separate that from what’s bad about the world wide web. From another angle: are there good things about the web that we can import to alleviate gopher’s shortcomings?
The discourse A recent thread of that conversation has been an exchange between ~solderpunk and ~enkiv2.
Retro web, simple web, and alternatives to the web A simple gopher client for Gnome, written in Vala This is in early stages, but it works fine for most gopher sites. I would like to find time to help out with it.
Shizaru, an opinionated web server This is a web server written in golang that attempts to “serve no evil” by imposing strong opinions on pages that it serves.
This blog is produced with hugo, a static site generator, and the articles are written in Markdown, a plain text markup format. Since the articles are fundamentally plain text, for some time I’ve been wanting to make them available over gopher, a simple protocol that was created around the same time as the first versions of the World Wide Web. I used gopher before I used the WWW in Lynx and Mosaic, and even after the web was dominant, I used GNOFN’s free dial-up gopher as my access point to the internet.