In response to Solerpunk’s 2024 OFFLine-FIRst SOftware CHallenge, I wrote a command line script for looking up flight ‘information’ offline.

One of the most noticeable things about Gemini is that it is text-based. Sure, it can support images but, depending on the client, these are mostly left hidden. Gemini gains a lot of its identity from this emphasis on text. One of the first things you’ll notice if you compare an average web page and a page on Gemini is that one is filled with images and highly visual, while the other is just a wall of text.

A few days ago on Mastodon, I came across a very useful toot by Fixato. He had provided a comprehensive shell command for updating you TLS certificates in light of the recent update to the agate server. He also kindly helped me troubleshoot additional issues I had.

Nothing much to report here. I updated the capsule structure to try make it more minimal and even easier to manage.

I’ve added a new ‘feed’ section to my capsule. It uses ‘comitium’ by alex/nytpu.

Problems, in the best sense

Much of the Gemini ‘content’ I’ve found so far, at least, some of the most engaging and unique, centers on technical questions about Gemini itself - how to set it up, navigate it, write in it, etc. These questions are usually accompanied by musings on what we can then do with this new protocol or about what Gemini ‘means’. Neither the answers to the technical questions, nor the accompanying speculations, are fully concrete. This is because both how Gemini works and what it can do remain somewhat vague. Yes, the broad brush-strokes have been laid down, but the smaller details have yet to be filled in. This is not a bad thing at all. Gemini is still in its very early stages. Much of its appeal stems from its huge potential.

Navigation

Part 1

A problem:

• ephemerality: content seems less ‘solid’ than on the web, less well mapped out and less defined.

A corresponding idea: