💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › 1636415395.bystand@zzo38co… captured on 2024-07-08 at 23:27:47. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-03-01)
-=-=-=-=-=-=-
From: news@zzo38computer.org.invalid
Subject: Re: Textual Web
Date: Mon, 08 Nov 2021 16:09:59 -0800
Message-ID: <1636415395.bystand@zzo38computer.org>
## mercury://
A stripped down version of gemini that was outlined by solderpunk in an
informal blog post. There is no actual spec for mercury and it is not
implemented anywhere. Mainly used by the gemini community as a stand-in
for the abstract idea of "gemini minus TLS" or "gemini minus feature x".
I had a idea to call "insecure-gemini", but I suppose "mercury" could be
another possibility (maybe is better; we will see what it is end up).
My proposal is that it is the same except without TLS, and without the 6x
reponse. (If the requested resource requires a client certificate, then it
can redirect to the corresponding "gemini" URL, and then the new request
will have a 6x response.) Other than that, everything else is the same as
the Gemini protocol (and the text/gemini file format is also the same, and
still is called "text/gemini" regardless of the protocol, even though the
URI scheme is different).
Is there already a name for MarkDown over HTTP(S)?
I don't know, but you can easily serve Markdown over HTTP(S) as well as
over Gemini (since either will allow the MIME type to be specified in
the response), although the client software might not support it. (Even
if the client software doesn't implement Markdown, it is still text based
format and so can still be displayed, so it isn't a too much problem.)
--
Don't laugh at the moon when it is day time in France.
Parent:
Textual Web (by David Arch <david@tilde.institute> on Wed, 27 Oct 2021 20:32:16 -0000 (UTC))
Children:
Re: Textual Web (by rtr <rtr@nospam.invalid> on Sun, 28 Nov 2021 06:42:30 +0800)