Introduction
Introduction Statistics Contact Development Disclaimer Help
I found a neat project today that I'm going to follow on Github. It
a QT5 and webkit based gopher browser written in Go. The project is
called prologic/gopherclient on Github. The author is currently in
process of converting it over to use a different http library so yo
have to checkout the webview branch. It still won't build, though.
There seems to be a small issue with the gopherproxy library it's
using.
Basically what it looks like user prologic has done is written a
gopher proxy (prologic/gopherproxy). He's then written a very simpl
webkit based http browser that uses the proxy library on the backen
to seamlessly render http requests in to gopher requests. This way
get a relatively modern "graphical" interface to gopher without
relying on a third party proxy like floodgap. Not that there's
anything wrong with using third party proxies. I just prefer to kee
it all local when I can.
I'm hoping to do some work to help the author with this project in
near future. I've already opened a few PRs and commented on the ope
issue for converting things to webview. Hopefully we'll sort things
out and have it working relatively soon.
In the mean time I've found a workaround solution. I'm running
prologic/gopherproxy in docker locally and pointing Firefox at
http://localhost:8000/<gopher-url>. It's not as seamless as the nat
browser would be; you're browsing to localhost followed by a slash
then the gopher url you want, but it's good enough for my needs rig
now. All I was hoping for was a slightly more graphical way to
interface with gopher sites since gopher now has some early support
for image and video files. So far, it's working out just fine.
https://github.com/prologic/gopherproxy
https://github.com/prologic/gopherclient
You are viewing proxied material from sdf.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.