No mention of gopher clients! How are you supposed to see other people’s posts? I found this one: http://gopher.quux.org:70/devel/gopher/Downloads/ which seems to work pretty well. I remember back in the day firefox/netscape used to support gopher:// url’s but pretty sure that’s no longer the case.
I use OverbiteFF on Firefox. Lynx also supports gopher. But where was the author’s gopher site? If it’s so easy (and it is [1]) why did he not do it himself? Seems odd.
The original article is posted on gopher here:
gopher://sdf.org/0/users/dbucklin/posts/how_gopher.txt
Lynx is a fantastic gopher browser and there are several new ones also in active development. There’s sacc(1) from the folks at bitreich.org and also VF-1 if you prefer more of a REPL style interface.
I’m going to take this rare opportunity to plug my gopher client: https://github.com/enkiv2/misc/blob/master/ncgopher.py – not because it’s particularly good, but because it’s a good illustration of how straightforward a featureful gopher client is to write.
I’m aware of a couple people on mastodon making much more polished & featureful clients. I can’t remember their names offhand, unfortunately.
You can use elinks, lynx, cgo, sacc (that you can try via ssh at ssh://kiosk@bitreich.org), clic, curl to download…
Most browsers can start an external program after downloading a file, (xdg-open by default). Gopher has text-menu but is not text-only.
Even plain netcat/telnet, given how simple is the protocol. If all you want is getting a document from gopher: printf '/0/%s\r\n' "$url" nc "$host" 70 > file.
Firefox dropped the gopher:// protocol support. moz :/ la…
No mention of gopher clients! How are you supposed to see other people’s posts? I found this one: http://gopher.quux.org:70/devel/gopher/Downloads/ which seems to work pretty well. I remember back in the day firefox/netscape used to support gopher:// url’s but pretty sure that’s no longer the case.
I use OverbiteFF on Firefox. Lynx also supports gopher. But where was the author’s gopher site? If it’s so easy (and it is [1]) why did he not do it himself? Seems odd.
[1] Not only do I run gopher but I wrote my own server, mainly to serve up my blog.
The original article is posted on gopher here: gopher://sdf.org/0/users/dbucklin/posts/how_gopher.txt
Lynx is a fantastic gopher browser and there are several new ones also in active development. There’s sacc(1) from the folks at bitreich.org and also VF-1 if you prefer more of a REPL style interface.
I’m going to take this rare opportunity to plug my gopher client: https://github.com/enkiv2/misc/blob/master/ncgopher.py – not because it’s particularly good, but because it’s a good illustration of how straightforward a featureful gopher client is to write.
I’m aware of a couple people on mastodon making much more polished & featureful clients. I can’t remember their names offhand, unfortunately.
You can use elinks, lynx, cgo, sacc (that you can try via ssh at
ssh://kiosk@bitreich.org), clic, curl to download…Most browsers can start an external program after downloading a file, (xdg-open by default). Gopher has text-menu but is not text-only.
Even plain netcat/telnet, given how simple is the protocol. If all you want is getting a document from gopher:
printf '/0/%s\r\n' "$url" nc "$host" 70 > file.Firefox dropped the gopher:// protocol support. moz :/ la…
Indeed it isn’t (and I think even the Firefox add-ons that added back support don’t work anymore…)
Haiku’s network protocol client layer has first-class Gopher support, and since our WebKit port uses our internal protocol stack, you can browse Gopher in WebPositive.
You can even do your social networking in gopher: https://blog.soykaf.com/post/gopher-support-in-pleroma/
I can’t really say it costs any effort at all if you are satisfied with the minimal: Here are the steps as author suggested:
So no apache module to setup? :P