Re: Re: Re: Hello Gemini

Previous Post

how many clients are actually doing TOFU

I've actually found that many clients follow TOFU. At least the ones that have more than a few commits in their repo. I use Amfora on CLI and Lagrange on GUI and Android. But I've tried a few others and they all usually throw up a message and ask if you want to trust the new cert.

It is part of the spec and there are enough GUI and TUI clients that are feature full and that should be something users look for. I mean, why not?

And if there's no identity behind it, we could as well generate certs every single day.

You could, and I think that eventually we would all start talking about it. Maybe that needs to happen.

I don't see *that* big differences between the two [markdown/gemtext].

To me the big difference is just how simple the implementations can be. For example, I can convert gemtext into HTML in about 4 lines of awk. And that is 4 lines of awk people who don't know awk could totally grok. Markdown is a bit more complex, having to understand inline items, multiple types of lists, tables, type fixing, etc. Yeah its nothing like HTML and CSS but the target here is text and media files. Links that point to text and media files. And if you look at all the other smolweb protocols they are all easily done this way too.

P.S. Is there any gemini indexer using that tags you're using at the bottom?

I stole that from a feature I added to an old perl blogging cgi script, which I think was taken from C Header file format for meta data used by some old IDE. Specifically the `$` wrapped stuff.

I actually use that in my atom.xml generator to add meta data to the feed. You can find that here.

atom.xml.py

$ published: 2025-08-02 15:30 $

$ tags: smolweb $

-- CC-BY-4.0 jecxjo 2025-08-02

Comments?

back

Proxied content from gemini://gemini.sh0.xyz/log/2025-08-02_re_re_re_hello_gemini.gmi

Gemini request details:

Original URL
gemini://gemini.sh0.xyz/log/2025-08-02_re_re_re_hello_gemini.gmi
Status code
Success
Meta
text/gemini
Proxied by
kineto

Be advised that no attempt was made to verify the remote SSL certificate.