💾 Archived View for rawtext.club › ~sloum › geminilist › 007481.gmi captured on 2023-11-14 at 08:34:29. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Charles Iliya Krempeaux cikrempeaux at gmail.com
Mon Nov 1 03:30:48 GMT 2021
- - - - - - - - - - - - - - - - - - -
Hello everyone,(And Happy Halloween for those who celebrate Halloween.)
This is my first time posting to this mailing list.
I implemented the Mercury Protocol as a Go library:
https://github.com/reiver/go-hg
This implementation includes both the client & server side of the MercuryProtocol.
For those familiar with the Go programming language — I tried to makepackage hg similar to Go's built-in "net/http" library. So that it wouldseem familiar; and thus hopefully easier to work with.
⁂
For me I prefer to separate out the TLS part from the server part. So, thisimplementation isn't an attempt to get rid of encryption, but instead a wayof dividing up the technology to make it easier to work with.
I was originally doing this in a Gemini Protocol Go implementation, andcalling the TLS-free version "naked Gemini". But when I started reading themailing list archive, and some of the gemlogs — still working through them— and noticed Mercury was the same thing, I created Go package hg.
Coincidentally, I was using TCP port 1961 for my "naked Gemini". I noticedsomeone else on the mailing list happened to pick that too. (Although fordifferent reasons that I did.)
⁂
Feedback is welcomed. If anyone has any questions, comments, or complaints,let me know.
--Charles Iliya Krempeaux, B.Sc.cikrempeaux at gmail.com-------------- next part --------------An HTML attachment was scrubbed...URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20211031/6d06d565/attachment.htm>