Mastodawn

Finger from 1971, Gopher from 1991, and Gemini from 2019. These protocols offer decentralized, terminal-based alternatives to the modern web. The small web's is in a renaissance. On the solarpunk philosophy of intentional technology, and how these protocols meet you where you are, whether you're on a machine from 2005 or just tired of Chrome's monoculture.

brennan.day

B 5d ago

Gemini, Gophers, and Fingers. Oh My! Alternative Internets Beyond HTTPS

https://brennan.day/gemini-gophers-and-fingers-oh-my-alternative-internets-beyond-https/

#GeminiProtocol #GopherProtocol #FingerProtocol #HTTP

Gemini, Gophers, and Fingers. Oh My! Alternative Internets Beyond HTTPS

brennan.day

Ramin Honary 6d ago

Crazy idea for #Emacs enthusiasts

On the #LispyGopherClimate podcast today, me, @screwlisp and @kentpitman had a fascinating conversation with @someodd .

During our conversation I remember her dropping this idea that the #GopherProtocol was all about menus. I remember this because she had said something like it in her Bartleby RFC document which I had read earlier, “But gopher is hierarchical. That’s the whole point. It’s a tree of menus, not a stream of content.” (I copy-pasted the section from which that quote comes below).

Just two weeks prior on the #LispyGopherClimate podcast we had a discussion with @chiply about “incremental completing read,” which was directly related to @karthink ‘s blog post on the Emacs Avy package.

So here is my crazy synthesis of the two: Emacs Avy as a Gopher client!!!

The incremental completing read pattern goes “Filter a list of results -> Select an item -> perform an action on the item.” The action could be to read the page, or to open a link that may trigger an “applet” action. I can see a whole new way to browse the Internet: no search engines, no LLM chat, just type what you think may exist and narrow down the list of all the content until you find something that you might want to read!

Is this post an attempt at humor, or am I just rambling? A little of each. I do want to try to build this thing, if anything to see how funny it would be to try to browse the Gopher network that way.

(Quoting @someodd )

I’ve been thinking a lot about how people in gopherspace – myself included – try too hard to make gopher be like the web. We abuse directories so we can have files with links. We call our writing “phlogs” which is just “blog” with a different letter, and then our phlogs end up looking like imitations of blogs anyway. Reverse chronological. Post after post. A timeline.

But gopher is hierarchical. That’s the whole point. It’s a tree of menus, not a stream of content. And the biggest abuse of gopher I see is people trying to flatten that hierarchy, trying to make it not-hierarchical, because that’s what the web trained us to expect.

So I started asking: what would sharing information look like if gopher had won? If the web never happened and something other than blogs took off? You wouldn’t have “posts.” You’d have a library. Subjects on shelves. You’d browse by walking through the stacks, not by scrolling a timeline.

That’s what bartleby is trying to be. Not a blog engine that speaks gopher, but a tool that takes the hierarchy seriously. Collections are the primary axis, not dates. Recent acquisitions exist, but they’re the display by the door, not the organizing principle.

gopher-proxy – /0//regarding_someodd/opensource/bartleby/bartleby-rfc.txt

LFA 🇮🇨May 25

Tengo mi madriguera gopher algo abandonailla y mi web más aún pero prometo escribir algo cuando pase la #LibreCan2026 mientras tanto podéis disfrutar de un montón de cosas interesantes en la web mediante el proyecto Planeta Libre de @victorhck
https://victorhck.gitlab.io/planetalibre/
y en Gopher / Gemini mediante el proyecto Chimaque de @caleb
gemini://caleb.subnet.city/directorio/

#SoftwareLibre #PlanetaLibre #Chimaque #GeminiProtocol #GopherProtocol

PlanetaLibre

YGGverse May 14

#phetch - #GopherProtocol client written in #Rust with #Tor / #I2P proxy support + #TLS as the bonus:
https://github.com/xvxx/phetch

To handle I2P connections use following trick:
TOR_PROXY=127.0.0.1:4447 target/release/phetch -o gopher://phlogqhspsjzcdubodidwc74pmc56hik2t3bhajwc47rg6snboia.b32.i2p:70/1ps/

GitHub - xvxx/phetch: 🐭 quick lil gopher client for your terminal

🐭 quick lil gopher client for your terminal. Contribute to xvxx/phetch development by creating an account on GitHub.

GitHub

YGGverse May 13

Testing #bodem - #GopherProtocol server written in #Rust

* gopher://phlogqhspsjzcdubodidwc74pmc56hik2t3bhajwc47rg6snboia.b32.i2p:70 - #I2P
* gopher://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]:70 - #Yggdrasil
* gopher://[505:6847:c778:61a1:5c6d:e802:d291:8191]:70 - #Mycelium

Some note about how to setup this server in multi-net environment using separated #systemd services (Ukr):
http://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]/d/249

P.S. take a look at PR as last official commit is 6-years old

YGGverse May 13

#GopherProtocol