Split Gemini spec into two specs?

[John Cowan]

On Tue, Feb 23, 2021 at 2:29 PM David Emerson <d at nnix.com> wrote:


> Though I agree with the principle, and it would make a lot of sense in
> many larger projects, binding the protocol tightly to the content is
> appropriate at this scale and for this purpose.


I think that makes sense for Gopher, but not for Gemini.  As we saw a day
or two ago, Gemini servers are designed to serve many files that are not
text/gemini, and are actually doing so.  Indeed, there is no reason that an
HTTP server can't serve text/gemini as well, and hopefully an HTTP proxy
will recognize text/gemini content and pass it through unchanged.

I feel pretty confident that the IETF will want them to be split.


John Cowan          http://vrici.lojban.org/~cowan        cowan at ccil.org
Almost all theorems are true, but almost all proofs have bugs.
        --Paul Pedersen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailing-list-archive.gemi.dev/www/attachments/20210223/a8dcc6c2/attachment-0001.htm>