I’m writing this blog outdoors, in accordance with the rules of Solderpunk’s ROOPHLOCH challenge. I’m also offline… there’s no Wifi here, and I have tethering turned off for my phone; I’ll turn it on for a minute when I’m done writing in order to publish it.
I’m sitting in a park or greenway that may or may not be closed to the public. This sign blocking the stairs to the boardwalk suggests that it is, but the corresponding wheelchair ramp isn’t blocked.
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.
Composing polls I have specifically not written support for creating polls yet.
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.
This is a recipe I got from somewhere online, but I’ve adapted it to my own preferences and general lack of willingness to measure ingredients, so now it’s mine. I make it a bit less than once a week, whenever we have black bean burritos. This is a very simple, minimalist guacamole, I think. If you’re quick at chopping vegetables, it only takes about 5-10 minutes to make.
Ingredients 1 small sweet onion (Vidalia or Palmetto Sweet), minced.
Since I’ve started reading gopher logs, I’ve noticed that a lot of people write very personal journals on their phlogs, where they are perhaps pseudonymous. I really want to write that kind of thing, but it wouldn’t work for me to have it on my blog or phlog. For one thing, my main online identities, like this blog, are tied to my public identity. And for another, I am a very private person.
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.