(proposal) on metadata in documents

[Solene Rapenne]

On Sun, 21 Feb 2021 13:06:53 -0000 (UTC)
text at sdfeu.org:

> Reading about favicon in Gemini by way of an extra request to the host 
> serving a requested document, I searched for "metadata" in old threads.
> 
> It seems to me the quoted message from 2020-11-14 below could serve as a 
> solution to the debate.
> 
> Note that the favicon RFC basically uses this approach itself, stating 
> some `key: value` pairs within the document.
> 
> => gemini://mozz.us/files/rfc_gemini_favicon.gmi RFC: Adding Emoji   
> Favicons to Gemini
> 
> Why not use this kind of structured metadata lines for an (as per RFC 
> still unmotivated) favicon convention?
> 
> Favicon: #
> 

It seems your are suggesting implementing equivalent of http headers
that are key: values pair and are not part of the document but is transmitted
in the reply. Currently gemini only returns the status code, the content type
and potentially the language (this is not mandatory).

That's an endless rabbithole that the Gemini protocol should better
not explore because it allows endless extendability.