[SPEC] Backwards-compatible metadata in Gemini

[easrng]

Many of us strongly believe in the one pageload generates one request
philosophy, including me, but metadata is also nice to have. While you
could put metadata in other files, that would result in multiple requests
being made. Instead, I am proposing a new file format,
text/gemini-metadata+json, to be used in data URIs in Gemtext. It would be
json (simply because it is popular and has wide support) with specified
keys. Possible things to include in the metadata could be a favicon (be it
emoji or otherwise), a theme color or color scheme to be used by the client
as it wishes, etc.
It would be used like this:

```
# My super cool gemsite
Welcome!

=> data:text/gemini-metadata+json;charset=utf-8,{"favicon":"?%E2%80%8D?"}
Page metadata
```

A Gemini client implementing this would add a check for links starting with
data:text/gemini-metadata+json to it's rendering code and when it
encounters one, decode it and take note of the metadata. Clients not
implenenting it will just see a link to the data, degrading (imo) quite
gracefully. I can't decide if the link should be hidden or not in browsers
with support though. If the link is hidden then the client should make sure
to expose the metadata elsewhere in the interface.
Please give all the feedback!

-- easrng
(Did I tag this right?)


-- 
? <https://www.google.com/teapot>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailing-list-archive.gemi.dev/www/attachments/20210221/e9da64b2/attachment.htm>