Gopher protocol

>>58155784
The day 4chan gets into Gopher will be my last day in the Web.

webassembly and websockets will be good maybe

>>58155784
Web had always it's two sides: source of knowledge and other content (I call it "Gopher" side), more or less organized and indexed by search engines. The other side, called by me "interactive", allows to communicate within web pages or on special platforms or protocols. Both sides have their pros and cons. Interesting for me is the influence that virtual realm makes on people in the 'real' world. Sometimes it is no longer possible to make a border between them; it's both fascinating and horrible. That's why I think that "Gopher" side of Internet is less dangerous and more 'comfy' to me.

>>58155784
No TLS for gopher is a total deal-breaker nowadays.

>>58155784
If Gopher could add multi user editing like Wikipedia it would be its comeback.

>>58155820
There is a gopher chan but It's pratically Dead

File: America.jpg (451KB, 1748x1816px) Image search: [Google]

451KB, 1748x1816px

>>58157037
There is actually a gopher interface to Wikipedia but it cannot be edited unfortunately
>>58156658
Couldn't it be run over Tor or i2p? You don't use JavaScript anyways, wouldn't it make sites much faster than using http?

>>58158772
What does JS have to do with encrypting and authenticating communication with a gopher server?

>>58155784
>Whatever happened to gopher?

Email > Web > Usenet > Archie > Gopher

Fuck Gopher