[SPEC] Backwards-compatible metadata in Gemini

Petite Abeille petite.abeille at gmail.com
Thu Feb 25 00:13:54 GMT 2021



> On Feb 25, 2021, at 00:48, Oliver Simmons <oliversimmo at gmail.com> wrote:
> 
> 1. The format and spec for metadata.

Perhaps it would be educative to take a look at the structure of your very own email, as per Message-ID: <CAFkF85aLmBEg5NM_a4+dnwDOWqsaktjOBoba3wT1CXuGasm=QA at mail.gmail.com>.

It looks a bit like this:

Content-Type: multipart/alternative; boundary="000000000000ac6dd305bc1dadab"

--000000000000ac6dd305bc1dadab
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

--000000000000ac6dd305bc1dadab
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

--000000000000ac6dd305bc1dadab--

Plain text. Rather self-explanatory.

This is called MIME, as in Multipurpose Internet Mail Extensions:

https://en.wikipedia.org/wiki/MIME

It's one of the fundamental building block of the internet, as we know it today. Even HTTP uses it.

Why would text/gemini need to reinvent it?

Why not use it just the way it is?

±0¢



More information about the Gemini mailing list