💾 Archived View for rawtext.club › ~sloum › geminilist › 007441.gmi captured on 2023-09-08 at 15:59:39. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Michael Lazar lazar.michael22 at gmail.com
Tue Oct 26 18:15:22 BST 2021
- - - - - - - - - - - - - - - - - - -
V1.0
Last-modified: 2021-10-26.
Developed by University of Minnesota in the early 90's. Peaked in the early90's. Gained a small resurgence in the 2000's. Gained a larger resurgence inthe late '10s with increased popularity coming from tilde servers and othersmall internet communities such as SDF and Bitreich.
=
gopher://floodgap.com
A forwards compatible extension for gopher developed by UMN in '93. Supportsform uploads, MIME types, and extra metadata queries. Uses the gopher://scheme. Was never widely adopted, and was not part of the 2000's gopherresurgence.
=
http://gopher.quux.org:70/Archives/mirrors/boombox.micro.umn.edu/pub/gopher/gopher_protocol/Gopher%2B/Gopher%2B.txt
Vanilla gopher wrapped in a TLS connection. Started circulating the gophermailing list around the time gemini was created. Not widely used (but didmanage to make it into curl!), and is primarily advocated by Bitreich members.
=
https://github.com/curl/curl/pull/6208
Information about this protocol is sparse, but at first glance it appears to bean amateurish blunder that should have just used a subset of HTTP/HTML. Doesn'tsupport inline images.
=
https://gemini.circumlunar.space/
A stripped down version of gemini that was outlined by solderpunk in aninformal blog post. There is no actual spec for mercury and it is notimplemented anywhere. Mainly used by the gemini community as a stand-in forthe abstract idea of "gemini minus TLS" or "gemini minus feature x".
=
gemini://gemini.circumlunar.space/users/solderpunk/gemlog/the-mercury-protocol.gmi
The "plaintext protocol", probably the closest thing we will get to a concreteimplementation of mercury. Created by gemini mailing list persona non grata,petite abeille. Supports both non-TLS and TLS, and is backwards compatible withgemini. Was originally referred to as "☿://".
=
https://textprotocol.org/
Companion protocol designed to work alongside gemini for file upload, by thecreator of Ariane.
=
https://codeberg.org/oppenlab/iapetus
Companion protocol designed to work alongside gemini for file upload, by AlexSchroeder. Notably implemented by the Lagrange browser.
=
https://transjovian.org:1965/titan
Companion protocol designed to work alongside gemini for file upload,independently proposed on the mailing list by Sean Conner and later benthor,who hosts a specification.
=
gemini://inimeg.space/
Borrows many design cues from gemini, but was built from the ground-up with adifferent set of design goals. Intended to exist as a separate protocol and not"augment" gemini (spartan is to gemini, as gemini is to gopher). No TLS.
=
gemini://spartan.mozz.us
Because sometimes in response to uploading files, someone will throw out a "youshould use FTP" as if that's not a loaded statement...
File transfer protocol that was created in the 70's. Contains lots of legacycruft because it was designed pre-TCP/IP, and is difficult to implement.
Plain FTP with a TLS layer added on top. Keeps all the cruft of FTP.
"SSH File Transfer Protocol". Despite the name, this is not FTP but a new filetransfer protocol designed to work on top of SSH.
Mail comments and questions about the FAQ to: lazar.michael22 at gmail.comCopyright (C) Michael Lazar 2021.This FAQ may be copied and redistributed under the terms of CC BY-SA 4.0.=
https://creativecommons.org/licenses/by-sa/4.0/