💾 Archived View for gemi.dev › gemini-mailing-list › 001053.gmi captured on 2023-11-04 at 13:17:41. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
# SMALL INTERNET PROTOCOL ROUNDUP V1.0 Last-modified: 2021-10-26. ## gopher:// Developed by University of Minnesota in the early 90's. Peaked in the early 90's. Gained a small resurgence in the 2000's. Gained a larger resurgence in the late '10s with increased popularity coming from tilde servers and other small internet communities such as SDF and Bitreich. => gopher://floodgap.com ## gopher+ A forwards compatible extension for gopher developed by UMN in '93. Supports form uploads, MIME types, and extra metadata queries. Uses the gopher:// scheme. Was never widely adopted, and was not part of the 2000's gopher resurgence. => http://gopher.quux.org:70/Archives/mirrors/boombox.micro.umn.edu/pub/gop her/gopher_protocol/Gopher%2B/Gopher%2B.txt ## gophers:// Vanilla gopher wrapped in a TLS connection. Started circulating the gopher mailing list around the time gemini was created. Not widely used (but did manage to make it into curl!), and is primarily advocated by Bitreich members. => https://github.com/curl/curl/pull/6208 ## gemini:// Information about this protocol is sparse, but at first glance it appears to be an amateurish blunder that should have just used a subset of HTTP/HTML. Doesn't support inline images. => https://gemini.circumlunar.space/ ## mercury:// A stripped down version of gemini that was outlined by solderpunk in an informal blog post. There is no actual spec for mercury and it is not implemented anywhere. Mainly used by the gemini community as a stand-in for the abstract idea of "gemini minus TLS" or "gemini minus feature x". => gemini://gemini.circumlunar.space/users/solderpunk/gemlog/the-mercury-protocol.gmi ## text:// The "plaintext protocol", probably the closest thing we will get to a concrete implementation of mercury. Created by gemini mailing list persona non grata, petite abeille. Supports both non-TLS and TLS, and is backwards compatible with gemini. Was originally referred to as "?://". => https://textprotocol.org/ ## iapeus:// Companion protocol designed to work alongside gemini for file upload, by the creator of Ariane. => https://codeberg.org/oppenlab/iapetus ## titan:// Companion protocol designed to work alongside gemini for file upload, by Alex Schroeder. Notably implemented by the Lagrange browser. => https://transjovian.org:1965/titan ## inimeg:// 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/ ## spartan:// Borrows many design cues from gemini, but was built from the ground-up with a different 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 # BONUS ROUND Because sometimes in response to uploading files, someone will throw out a "you should use FTP" as if that's not a loaded statement... ## ftp:// File transfer protocol that was created in the 70's. Contains lots of legacy cruft because it was designed pre-TCP/IP, and is difficult to implement. ## ftps:// Plain FTP with a TLS layer added on top. Keeps all the cruft of FTP. ## sftp:// "SSH File Transfer Protocol". Despite the name, this is not FTP but a new file transfer protocol designed to work on top of SSH. # Contact Mail comments and questions about the FAQ to: lazar.michael22 at gmail.com Copyright (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/
This. I like it. Question: Other than Usenet and BBS's, are there any protocols that are purely message-board centric? On 10/26/21 12:15 PM, Michael Lazar wrote: > # SMALL INTERNET PROTOCOL ROUNDUP > > V1.0 > > Last-modified: 2021-10-26. > > ## gopher:// > > Developed by University of Minnesota in the early 90's. Peaked in the early > 90's. Gained a small resurgence in the 2000's. Gained a larger resurgence in > the late '10s with increased popularity coming from tilde servers and other > small internet communities such as SDF and Bitreich. > > => gopher://floodgap.com > > ## gopher+ > > A forwards compatible extension for gopher developed by UMN in '93. Supports > form uploads, MIME types, and extra metadata queries. Uses the gopher:// > scheme. Was never widely adopted, and was not part of the 2000's gopher > resurgence. > > => http://gopher.quux.org:70/Archives/mirrors/boombox.micro.umn.edu/pub/g opher/gopher_protocol/Gopher%2B/Gopher%2B.txt > > ## gophers:// > > Vanilla gopher wrapped in a TLS connection. Started circulating the gopher > mailing list around the time gemini was created. Not widely used (but did > manage to make it into curl!), and is primarily advocated by Bitreich members. > > => https://github.com/curl/curl/pull/6208 > > ## gemini:// > > Information about this protocol is sparse, but at first glance it appears to be > an amateurish blunder that should have just used a subset of HTTP/HTML. Doesn't > support inline images. > > => https://gemini.circumlunar.space/ > > ## mercury:// > > A stripped down version of gemini that was outlined by solderpunk in an > informal blog post. There is no actual spec for mercury and it is not > implemented anywhere. Mainly used by the gemini community as a stand-in for > the abstract idea of "gemini minus TLS" or "gemini minus feature x". > > => gemini://gemini.circumlunar.space/users/solderpunk/gemlog/the-mercury-protocol.gmi > > ## text:// > > The "plaintext protocol", probably the closest thing we will get to a concrete > implementation of mercury. Created by gemini mailing list persona non grata, > petite abeille. Supports both non-TLS and TLS, and is backwards compatible with > gemini. Was originally referred to as "?://". > > => https://textprotocol.org/ > > ## iapeus:// > > Companion protocol designed to work alongside gemini for file upload, by the > creator of Ariane. > > => https://codeberg.org/oppenlab/iapetus > > ## titan:// > > Companion protocol designed to work alongside gemini for file upload, by Alex > Schroeder. Notably implemented by the Lagrange browser. > > => https://transjovian.org:1965/titan > > ## inimeg:// > > 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/ > > ## spartan:// > > Borrows many design cues from gemini, but was built from the ground-up with a > different 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 > > # BONUS ROUND > > Because sometimes in response to uploading files, someone will throw out a "you > should use FTP" as if that's not a loaded statement... > > ## ftp:// > > File transfer protocol that was created in the 70's. Contains lots of legacy > cruft because it was designed pre-TCP/IP, and is difficult to implement. > > ## ftps:// > > Plain FTP with a TLS layer added on top. Keeps all the cruft of FTP. > > ## sftp:// > > "SSH File Transfer Protocol". Despite the name, this is not FTP but a new file > transfer protocol designed to work on top of SSH. > > # Contact > > Mail comments and questions about the FAQ to: lazar.michael22 at gmail.com > Copyright (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/ -- ----- http://singletona082.flounder.online gemini://singletona082.flounder.online My online presence
I think there's also git:// and ssh:// Personally, I think it will be good to replace URL's with something that shows more explicitly the commands used to retrieve or interact with the resource. On Tue, Oct 26, 2021 at 1:15 PM Michael Lazar <lazar.michael22 at gmail.com> wrote: > # SMALL INTERNET PROTOCOL ROUNDUP > > V1.0 > > Last-modified: 2021-10-26. > > ## gopher:// > > Developed by University of Minnesota in the early 90's. Peaked in the early > 90's. Gained a small resurgence in the 2000's. Gained a larger resurgence > in > the late '10s with increased popularity coming from tilde servers and other > small internet communities such as SDF and Bitreich. > > => gopher://floodgap.com > > ## gopher+ > > A forwards compatible extension for gopher developed by UMN in '93. > Supports > form uploads, MIME types, and extra metadata queries. Uses the gopher:// > scheme. Was never widely adopted, and was not part of the 2000's gopher > resurgence. > > => > http://gopher.quux.org:70/Archives/mirrors/boombox.micro.umn.edu/pub/goph er/gopher_protocol/Gopher%2B/Gopher%2B.txt > > ## gophers:// > > Vanilla gopher wrapped in a TLS connection. Started circulating the gopher > mailing list around the time gemini was created. Not widely used (but did > manage to make it into curl!), and is primarily advocated by Bitreich > members. > > => https://github.com/curl/curl/pull/6208 > > ## gemini:// > > Information about this protocol is sparse, but at first glance it appears > to be > an amateurish blunder that should have just used a subset of HTTP/HTML. > Doesn't > support inline images. > > => https://gemini.circumlunar.space/ > > ## mercury:// > > A stripped down version of gemini that was outlined by solderpunk in an > informal blog post. There is no actual spec for mercury and it is not > implemented anywhere. Mainly used by the gemini community as a stand-in for > the abstract idea of "gemini minus TLS" or "gemini minus feature x". > > => gemini:// > gemini.circumlunar.space/users/solderpunk/gemlog/the-mercury-protocol.gmi > > ## text:// > > The "plaintext protocol", probably the closest thing we will get to a > concrete > implementation of mercury. Created by gemini mailing list persona non > grata, > petite abeille. Supports both non-TLS and TLS, and is backwards compatible > with > gemini. Was originally referred to as "?://". > > => https://textprotocol.org/ > > ## iapeus:// > > Companion protocol designed to work alongside gemini for file upload, by > the > creator of Ariane. > > => https://codeberg.org/oppenlab/iapetus > > ## titan:// > > Companion protocol designed to work alongside gemini for file upload, by > Alex > Schroeder. Notably implemented by the Lagrange browser. > > => https://transjovian.org:1965/titan > > ## inimeg:// > > 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/ > > ## spartan:// > > Borrows many design cues from gemini, but was built from the ground-up > with a > different 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 > > # BONUS ROUND > > Because sometimes in response to uploading files, someone will throw out a > "you > should use FTP" as if that's not a loaded statement... > > ## ftp:// > > File transfer protocol that was created in the 70's. Contains lots of > legacy > cruft because it was designed pre-TCP/IP, and is difficult to implement. > > ## ftps:// > > Plain FTP with a TLS layer added on top. Keeps all the cruft of FTP. > > ## sftp:// > > "SSH File Transfer Protocol". Despite the name, this is not FTP but a new > file > transfer protocol designed to work on top of SSH. > > # Contact > > Mail comments and questions about the FAQ to: lazar.michael22 at gmail.com > Copyright (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/ >
On Tue, Oct 26, 2021 at 6:05 PM Andrew Singleton <singletona082 at gmail.com> wrote: > > This. I like it. > > Question: > Other than Usenet and BBS's, are there any protocols that are purely message-board centric? Not that I'm aware of. There's all of the fediverse peer-to-peer stuff (ActivityPub, Scuttlebutt, etc.) but I don't consider that to be in the same category as this list and I'm not very familiar with them. There are probably more than a dozen message boards built on top of Gopher and Gemini, most of them modelled after chan-style image boards or traditional web forums. gemini://station.marinrue.com is the only one I know of that takes a shot at copying a twitter-like social feed. Also, maybe it's just the circles that I hang out in, but BBS (over telnet) seems to be rising in popularity again. Best, Michael
On 10/27/2021 12:03 PM, Michael Lazar wrote: > On Tue, Oct 26, 2021 at 6:05 PM Andrew Singleton > <singletona082 at gmail.com> wrote: >> >> This. I like it. >> >> Question: >> Other than Usenet and BBS's, are there any protocols that are purely message-board centric? > > Not that I'm aware of. There's all of the fediverse peer-to-peer stuff > (ActivityPub, Scuttlebutt, etc.) but I don't consider that to be in > the same category as this list and I'm not very familiar with them. > > There are probably more than a dozen message boards built on top of > Gopher and Gemini, most of them modelled after chan-style image boards > or traditional web forums. gemini://station.marinrue.com is the only > one I know of that takes a shot at copying a twitter-like social feed. > > Also, maybe it's just the circles that I hang out in, but BBS (over > telnet) seems to be rising in popularity again. > > Best, > Michael > That they certainly are; I have accounts on several, some over SSH as well as Telnet.
Don?t forget the classic, Finger Alex > On Oct 26, 2021, at 10:35 AM, Michael Lazar <lazar.michael22 at gmail.com> wrote: > > ?# SMALL INTERNET PROTOCOL ROUNDUP > > V1.0 > > Last-modified: 2021-10-26. > > ## gopher:// > > Developed by University of Minnesota in the early 90's. Peaked in the early > 90's. Gained a small resurgence in the 2000's. Gained a larger resurgence in > the late '10s with increased popularity coming from tilde servers and other > small internet communities such as SDF and Bitreich. > > => gopher://floodgap.com > > ## gopher+ > > A forwards compatible extension for gopher developed by UMN in '93. Supports > form uploads, MIME types, and extra metadata queries. Uses the gopher:// > scheme. Was never widely adopted, and was not part of the 2000's gopher > resurgence. > > => http://gopher.quux.org:70/Archives/mirrors/boombox.micro.umn.edu/pub/g opher/gopher_protocol/Gopher%2B/Gopher%2B.txt > > ## gophers:// > > Vanilla gopher wrapped in a TLS connection. Started circulating the gopher > mailing list around the time gemini was created. Not widely used (but did > manage to make it into curl!), and is primarily advocated by Bitreich members. > > => https://github.com/curl/curl/pull/6208 > > ## gemini:// > > Information about this protocol is sparse, but at first glance it appears to be > an amateurish blunder that should have just used a subset of HTTP/HTML. Doesn't > support inline images. > > => https://gemini.circumlunar.space/ > > ## mercury:// > > A stripped down version of gemini that was outlined by solderpunk in an > informal blog post. There is no actual spec for mercury and it is not > implemented anywhere. Mainly used by the gemini community as a stand-in for > the abstract idea of "gemini minus TLS" or "gemini minus feature x". > > => gemini://gemini.circumlunar.space/users/solderpunk/gemlog/the-mercury-protocol.gmi > > ## text:// > > The "plaintext protocol", probably the closest thing we will get to a concrete > implementation of mercury. Created by gemini mailing list persona non grata, > petite abeille. Supports both non-TLS and TLS, and is backwards compatible with > gemini. Was originally referred to as "?://". > > => https://textprotocol.org/ > > ## iapeus:// > > Companion protocol designed to work alongside gemini for file upload, by the > creator of Ariane. > > => https://codeberg.org/oppenlab/iapetus > > ## titan:// > > Companion protocol designed to work alongside gemini for file upload, by Alex > Schroeder. Notably implemented by the Lagrange browser. > > => https://transjovian.org:1965/titan > > ## inimeg:// > > 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/ > > ## spartan:// > > Borrows many design cues from gemini, but was built from the ground-up with a > different 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 > > # BONUS ROUND > > Because sometimes in response to uploading files, someone will throw out a "you > should use FTP" as if that's not a loaded statement... > > ## ftp:// > > File transfer protocol that was created in the 70's. Contains lots of legacy > cruft because it was designed pre-TCP/IP, and is difficult to implement. > > ## ftps:// > > Plain FTP with a TLS layer added on top. Keeps all the cruft of FTP. > > ## sftp:// > > "SSH File Transfer Protocol". Despite the name, this is not FTP but a new file > transfer protocol designed to work on top of SSH. > > # Contact > > Mail comments and questions about the FAQ to: lazar.michael22 at gmail.com > Copyright (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/
> Question: > Other than Usenet and BBS's, are there any protocols that are purely message-board centric? > Well, I guess there was Fido net. https://en.m.wikipedia.org/wiki/FidoNet
> On Oct 27, 2021, at 12:46, Alex <alex at alexwennerberg.com> wrote: > > ?Don?t forget the classic, Finger The original homepage! Emma H
---