Earlier quoted context omitted.
"Lack of HTTPS on the author's site also adds a nice subtle flavour to the blogpost." This blog can be read over TLS using gemini://. printf 'gemini://gemini.conman.org/boston/2022/09/22.1\r\n' \ |openssl s_client -connect 71.19.142.20:1965 -ign_eof Also https://portal.mozz.us/gemini/gemini.conman.org/boston/2022/...
Do either of these address the underlying problem that without https there's no guarantee that the blog content hasn't been modified in transit? Neither Gemini nor the Internet Archive have access to the content through a channel other than the insecure HTTP endpoint, right?
All Gemini is signed. [0] It's mandatory. That's why the parent piped through openssl to connect.
For example, the page that we're looking at is signed. [1] (Using a bridge to show the certificate, but you can verify it yourself, as well.)
[0] https://gemini.circumlunar.space/docs/specification.html
[1] https://portal.mozz.us/gemini/gemini.conman.org/boston/2022/...