💾 Archived View for rawtext.club › ~sloum › geminilist › 001251.gmi captured on 2020-09-24 at 02:00:33. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Petite Abeille petite.abeille at gmail.com
Tue Jun 2 20:57:27 BST 2020
- - - - - - - - - - - - - - - - - - -
On Jun 2, 2020, at 21:26, solderpunk <solderpunk at SDF.ORG> wrote:
As of yesterday, the freeze is over! The spec is now "liquid" once again.
Cool. Can we remove things? :)
❶ drop ;charset= from text/gemini content-type response. Everything is UTF-8. Gemini doesn't support legacy encodings.
Rational: Clients shouldn't burden themselves with legacy charset conversions, which is finicky. Servers are better placed to normalize encoding if they must. Gemini is about the future, not the past (EBCDIC 273 anyone?).
❷ drop everything from text/gemini but text and link lines.
Rational: The world has enough formatting options as it is. Everybody and their pet fish has their preferences (most posts on this list are about formatting...). text/gemini will not move the state of the art. Keep it simple. Less is more.
❸ mandate
= TLS 1.3. Drop legacy support.
Rational: no point dragging the burden of the past into the future. Gemini innovative take on TLS deserves a modern foundation.
In short, Mercury over TLS [1] :)
Networking Truths #12 [2]:
In protocol design, perfection has been reached not when thereis nothing left to add, but when there is nothing left to take away.
This would make Saint-Exupéry proud.
[1] https://portal.mozz.us/gemini/gemini.circumlunar.space/users/solderpunk/cornedbeef/the-mercury-protocol.gmi[2] https://tools.ietf.org/html/rfc1925
-------------- next part --------------An HTML attachment was scrubbed...URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200602/3d68568c/attachment-0001.htm>