 |
I found a neat project today that I'm going to follow on Github. It's |
|
a QT5 and webkit based gopher browser written in Go. The project is |
|
called prologic/gopherclient on Github. The author is currently in the |
|
process of converting it over to use a different http library so you |
|
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 simple |
|
webkit based http browser that uses the proxy library on the backend |
|
to seamlessly render http requests in to gopher requests. This way you |
|
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 keep |
|
it all local when I can. |
|
|
|
I'm hoping to do some work to help the author with this project in the |
|
near future. I've already opened a few PRs and commented on the open |
|
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 native |
|
browser would be; you're browsing to localhost followed by a slash and |
|
then the gopher url you want, but it's good enough for my needs right |
|
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 |
