There are far more gopher phlogs than gemini gemlogs.
Still, both communities overlap of course.
Setting up a gopher phlog requires no TLS at all and any machine from 1980 (even maybe ITS
with a Gopher client written in MacLisp) will be able to read it with no issues.
that's another large chunk of gemini; rehosted gopherholes. Which is silly unless the originals aren't accessible anymore since gopher is already a minimalist protocol
They render better on Smartphones. Lagrange and such do a good job but is not perfect.
Oddly, the best client for Android (albeit clunky) has been Emacs+Elpher as it has the perfect options for word wrapping.
Altough as most Gopher sites are hosted under Unix, running fmt/fold/par on files is a non-issue modulo ASCII ART and inline code with hard requeriments on indentation (TCL for instance on code blocks) or Python.
takes a url to a regular webpage and spits out a gemtext version that is much more sparse and, for me, is much more readable.
For example, here's this very website:
gemini://gemi.dev/cgi-bin/waffle.cgi/feed?https%3A%2F%2Fnews.ycombinator.com%2Frss
it's honestly the only reason I still use gemini since the rest of it is abandoned gemlogs, rehosts of web content I don't care or ersatz social media