I hold the controversial opinion that encryption can be an anti-feature on the "small web". One of the reason is technical: encryption takes computing resources, and can hardly be made time proof, as it has to evolve in response to threats, and certificates tend to have expiration dates. The other is more philosophical: you use encryption when you want to share secrets: personal data, passwords, credit card numbers, etc... A system that doesn't support encryption doesn't support transfer of personal data, accounts or commercial transactions, which I believe is a good thing in this niche. There is no shortage of secure communication systems when you need one, let that niche stay a niche.
Your point about not having encryption is really quite interesting to me. I would want to add some form of signing to prove something came from somewhere unaltered, but that would go against the idea.
unset LESSOPEN
or have it at ~/.profile.Reticulum it's unusable in 32 bit machines, it badly needs a Go port for nomadnet.
On Gopher, well, lynx/sacc and maybe i2pd for some security and anonimity.
As a start, there's:
gopher://magical.fish
gopher://sdf.org
For gemini, gemini://gemi.dev it's nice.
'Lagrange' covers both gemini and gopher as a client.You can set an HTTPS proxy for it and read news sites and blogs over Gemini.
Just set
stargate.gemi.dev:1994
As the HTTP proxy in the settings for Lagrange.For the terminal guys, there's Telescope and it can use HTTP proxies as well. Read the man page.
There are also a few variants of Rust ports too (i like https://github.com/zevaryx/rettui for a full nomadnet replacement)
I recently built a Gemini client for people who like GUI's more than TUI's, and want a native macOS app