remember gopher
http won the internet over
if you are going to browse gopher sites
you might wanna install Netscape navigator 4
it's really the only browser I use for this protocol
tell me some of your experiences /g/
>>61547373
I use lynx because I'm a normal person.
Though not quite so normal that I don't use Gopher it seems.
>>61547373
Firefox with the Overbite add-on
There's a few cool file sharing gopher holes out there, but there's also a lot of empty proof of concept sites too.
Good gopher sites?
Also, is there a search engine?
>>61548895
gopher://gopher.floodgap.com/1/v2
>>61547373
>Netscape navigator 4
What about Mozilla pre-removal of Gopher support?
https://ftp.mozilla.org/pub/mozilla/releases/
I believe 1.8b1 would be the last, the "fix" came in 1.9.
>>61547404
>lynx
>anime
>normal person
Pick none
>>61549795
I just downloaded and installed it on a Debian box so seems to still be in good shape dependency-wise
>gopher
You mean just the same few SDF.org blogs?
>>61548854
Is Overbite a Web Extension (will it survive FF 57)?
>>61554130
Considering the site says it needs Firefox 38 I don't think it's been touched in years.
>>61549911
I'd never thought i'd see this thread in gopher form.
cool
>>61556102
>>61554130
https://addons.mozilla.org/en-US/firefox/addon/overbiteff/
It was actually last updated in March this year, but:
>It is with great sadness we note that, because appropriate APIs are not currently available for WebExtensions, OverbiteFF will cease functioning with Firefox 56. See bugs 1247628 and 1310427. It is hoped Mozilla will rectify this situation soon.
So RIP
Is there any advantage of using Gopher vs http?
>>61556628
That's a bummer. Guess I'll be sticking with lynx for the foreseeable future then.
>>61556688
Realistically? Not really, not these days. The simplicity could be done just as well by using just pure HTML and very minimal (optional) CSS.
I didn't know Gopher had hot animu girls
http://gopher.floodgap.com/gopher/gw?gopher://gopher.meulie.net:70/0/textfiles/art/ASCIIPR0N/anime14.txt
http://gopher.floodgap.com/gopher/gw?gopher://gopher.meulie.net:70/0/textfiles/art/ASCIIPR0N/anime20.txt
>>61556804
NSFW link:
http://gopher.floodgap.com/gopher/gw?gopher://gopher.meulie.net:70/0/textfiles/art/ASCIIPR0N/anime47.txt
>>61556688
Gopher is simpler to setup (once you know it exists at least) and the protocol is more lightweight. Compare https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Example_session with https://en.wikipedia.org/wiki/Gopher_(protocol)#Protocol. But given today's network speeds, the difference isn't really appreciable for normal cases.
More important I think is the Gopher philosophy. A gopherhole is structured exactly like a typical hierarchical filesystem, and all gopherholes look and navigate the same way. Plaintext is the primary format for content. HTTP mainly deals with HTML, and especially with the advent of Javascript, websites can operate in vastly different ways from each other.
Lack of features isn't always a bad thing either. The evolution of HTTP and the web has introduced tracking, ads, DRM, websites that reply on special proprietary extensions and break on other web browsers/operating systems, etc... Partly by design but mostly by simply not being a mainstream technology since the web took off, Gopher has remained "pure".
>>61556951
>But given today's network speeds, the difference isn't really appreciable for normal cases.
You could even argue that, due to the lower resources of most gopher servers that they'll be slower than HTTP, despite the technical advantage of the protocol.
But yes, it's the philosophy of gopher that really makes it shine, especially as I'm a lover of text files (that sounded less autistic in my head). Though really you can use <pre> tags in html to get something very similar to gopher.
>>61557315
I think both protocols can have their place. While you can get something very similar to gopher, it's more effort than just using gopher when the content is very simple.
The main drawback of course is that most people have web browsers and not gopher clients. For that, I think something like pygopherd is an excellent answer, which both acts as a normal Gopher server and an HTTP server, translating Gopher menus to HTML. That gives you the advantages of the ease and simplicity of gopher while still being accessible to everyone without needing to use a "gateway" like Floodgap.
For example, >>61549911 can also be viewed at http://khzae.net/1/phourchan/g/61547373.