💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › tned7s$6fd$1@gioia.aioe.or… captured on 2024-07-09 at 00:02:49. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-01-29)

-=-=-=-=-=-=-

Re: Gemini client for legacy systems.

Message headers

From: Martin <martin@datapulp.de>

Subject: Re: Gemini client for legacy systems.

Date: Thu, 15 Dec 2022 07:01:30 +0100

Message-ID: <tned7s$6fd$1@gioia.aioe.org>

Message content

Am 11.12.22 um 14:23 schrieb Pepinno The Great:

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

> machines?

Gemini is no retro protocol.

> 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.

It can. I you like you can transfer html 2.0 pages via Gemini transfer

protocol, as any other file type.

Please keep in mind, that all security demands, like advancing TLS

standards, are kept for security reasons - in general, not just for

Gemini. These are not toys to play on retro machines, but modern

standards with the aim of securing transports of data.

If you'd like to run old software, Gemini is already out of scope.

Martin

Related

Parent:

Re: Gemini client for legacy systems. (by pepinno@thinkpad.naleco.com.NOSPAM (Pepinno The Great) on Sun, 11 Dec 2022 14:23:12 +0100)

Start of thread:

Gemini client for legacy systems. (by Anthk <anthk@disroot.org> on Mon, 10 Oct 2022 21:05:43 -0000 (UTC))