💾 Archived View for rawtext.club › ~sloum › geminilist › 001859.gmi captured on 2020-10-31 at 02:34:05. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Hannu Hartikainen hannu.hartikainen+gemini at gmail.com
Tue Jun 23 21:33:15 BST 2020
- - - - - - - - - - - - - - - - - - -
On Tue, 23 Jun 2020 at 19:17, William Casarin <jb55 at jb55.com> wrote:
setting it up is not the issue. I'm just not a fan of the extra
complexity and latency[1]. I would prefer to use a protocol that is as
snappy as gopher but with a nicer syntax that is more markdown-friendly.
Mercury seems to fit that bill quite nicely.
The Gemini spec does not *require* TCP, so similar levels of snappinesscould be achieved with QUIC. It does the connection handshakesimultaneously with the TLS handshake, ending up with no more handshakemessages than the classical TCP SYN / SYN+ACK / ACK handshake.
You could get still snappier with a connectionless protocol. I justcaptured a single page load of Gopherpedia using Wireshark. Guess how manyEthernet frames? 11. These text based protocols are not optimized for speedor simplicity (as in minimizing abstraction layers). We are all standing onthe shoulders of giants.
-Hannu-------------- next part --------------An HTML attachment was scrubbed...URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200623/5aa92565/attachment.htm>