In some respects HN is a Gopher server adapted for today. Focused on content, links to information, and just enough detail to keep you going.
As a protocol, Gopher is straight forward. Whenever someone talks about the "semantic web" I'm always reminded of Gopher has been doing since 1991. It is in no way perfect, but worked well.
I like to use gopher for early demonstrations that some low-level networking code works or how it should be used. It is certainly easier to write working gopher client/server than to deal with intricacies of HTTP or most other protocols when you want to test that TCP stack or code that breaks down incoming byte stream into lines actually works.
And I'm seriously considering writing GUI gopher client as an all-encompassing example in dfsch.
Gopher?! Why? Also, I'm pretty sure the reason most Gopher clients were abandoned was in fact due to the explicit lack of coffee making, you might want to at least make some attempt at an implementation...
[+] [-] enneff|15 years ago|reply
[+] [-] indrora|15 years ago|reply
[+] [-] davidblair|15 years ago|reply
As a protocol, Gopher is straight forward. Whenever someone talks about the "semantic web" I'm always reminded of Gopher has been doing since 1991. It is in no way perfect, but worked well.
[+] [-] gjm11|15 years ago|reply
[+] [-] synack|15 years ago|reply
gopher://synack.me/
[+] [-] jey|15 years ago|reply
I have fond memories of spelunking around gopher servers back in 1993. :)
[+] [-] dfox|15 years ago|reply
And I'm seriously considering writing GUI gopher client as an all-encompassing example in dfsch.
[+] [-] beaumartinez|15 years ago|reply