💾 Archived View for geminiprotocol.net › history › phlog › featherweight-text-protocols.gmi captured on 2024-05-12 at 15:18:06. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Featherweight text protocols

(originally posted in Gopherspace on 2019-06-21)

Alex Schroeder recently wrote a server and client for a very simple text-only protocol which he described as being "basically Gopher without the menus". This inspired me to offer, on Mastodon, the following impromptu ultra-minimalist protocol specification:

All connections are TLS secured
Requests are a UTF-8 encoded selector and a CLRF, nothing more
Responses are guaranteed UTF-8 encoded text
No further structure of response is guaranteed
Clients should be able to extract any URLs from anywhere in the text and construct a menu, with interface of their own choosing.

Alex's system doesn't actually quite meet this criteria, but it's very close. I have started thinking of protocols like the above as "featherweight" protocols. If you ignore the TLS part, the above is actually a *subset* of standard gopher!

Alex Schroeder's 2019-06-18 post on "A simple text server"

Alex Schroeder's 2019-06-19 post on "A simple text client"

I imagine the above featherlight spec might be popular with ratfactor, who recently wrote that:

Faced with gopher's confusing and unreliable approach of allowing a server to deliver absolutely anything while offering almost no way to provide information as to what's being served, they would prefer to make things more simple and less flexible by just limiting things to UTF-8, rather than make things more complex and more powerful by adding MIME types. That's every bit as valid a response to the problem.
They were tempted to suggest a system where links be presented as raw URLs with any friendly text for the user.

Ratfactor's 2019-06-18 post

I always really enjoy pushing the limits of minimalism, and I think ideas like these do precisely that. I actually expect that with a bit of work, systems like these could be made fairly comfortable. While they are less capable than gopher, they could support the vast majority of a typical gopher enthusiast's daily use, like reading phlogs. Imagine, gopher menus as bloat!

Ultimately, a featherweight protocol isn't the direction I want to take Project Gemini in, but don't take that as a disparagement of the idea. I think they're really nifty, and I'm definitely interested to read more ideas or experiments along these lines. Some featherweight clients might make very usable "emergency clients" for a lot of Gemini content!