Re: Gemini client for legacy systems.

Message headers

From: pepinno@thinkpad.naleco.com.NOSPAM (Pepinno The Great)

Subject: Re: Gemini client for legacy systems.

Date: Sun, 11 Dec 2022 14:23:12 +0100

Message-ID: <072h6j-48n.ln1@intheattic.eternal-september.org>

bacardi55 <bac@rdi55.pl> wrote:

On dim., 11. déc. 00:09, Pepinno The Great wrote:

> Does the Gemini protocol mandates TLS 1.2 or higher?

Yes. From the official spec:

"Servers MUST use TLS version 1.2 or higher and SHOULD use TLS version

1.3 or higher"

https://gemini.circumlunar.space/docs/specification.gmi

Then it is gopher all the way for me.

What kind of retro protocol is that which cannot be run on retro

machines? Gemini can get a ride, for all I care.

If the gemini scheme is intended for modern machines (because of its high

version TLS demands), and not for retro machines (which lack such high

version TLS support), then why cannot the gemini goals be accomplished

with just HTML 2.0: that would mean no CSS, no tables, no JavaScript,

and basic form submission capability. Denote it by a new protocol name,

HTTP1:// and be done with it? All the effort to make a "new standard"

would be then spared, as the new standard would be just cherry-picking a

subset of what already exists.

Parent:

Start of thread:

Children: