Slashdot Mirror


When was the Last Time You Used Gopher?

ahuber asks: "As part of a class for LIS 391 @ the University of Illinois, I'm doing a history of the gopher protocol. My intent in this is to track the rise and fall of old technologies in hope that it tells us something about technologies we use today. So, my question to you is: When was the last time you used a gopher server? What did you use it for? And finally, do you miss the gopher now that its virtually gone? While some of you may think this is a silly topic, old and useful technologies are going the way of Gopher every day. One example from my campus is the retiring of the newsgroup server and telnet. Do you have any similar experiences that made you think twice about giving up an older technology?"

15 of 127 comments (clear)

  1. The last time I used Gopher by xagon7 · · Score: 4, Interesting

    Was when I wrote the "Atomic Mp3 Finder" about 2 months before Napster came out.

    It was a piece of shit, as I was still new to development, but was fun, and I learned a TON.

  2. Are there any benifits of Gopher vs the Web? by T-Ranger · · Score: 3, Interesting
    I remember using Gopher back in 1994 via Lynx on a text based dialup. Even viewing both via text, the web was infinitly better. While it may not be a requirement of the technology, all the gopher sites I went to were hierarchically based, with no cross linking. Some data hadent been webified, so gopher was still usefull, but it sucked.

    Are there any benifits of Gopher over http/html at all?

  3. a bit of time ago by eamonman · · Score: 2, Interesting

    Jeez, I last used a gopher client nine years ago, when I was an incoming frosh in college and had no idea what http, ftp, or gopher meant. I recall that at the time, people were still using gopher for researching things, but that was quickly tapering off. We all were starting to use web search engines like infoseek or lycos or altavista (or was that more recent) to do research for school projects.

    --
    0- Eamonman Proud member of DNRC
  4. About two weeks ago by keesh · · Score: 2, Interesting

    I was testing out mozilla's gopher:// handler. It actually works :)

    1. Re:About two weeks ago by caseih · · Score: 2, Interesting

      Until recently, BYU had totally forgotten about their gopher server which was running without any changes for the last 7 years or so. gopher://gopher.byu.edu. I don't know if it is down now, or is just firewalled off.

  5. Back when I was a Golden Gopher myself by Saganaga · · Score: 4, Interesting

    I think the only time I used Gopher was when I was a student back at the University of Minnesota (whose mascot, the Golden Gopher, provided the inspiration for the protocol's name for those at the U of M who developed it). I think that was 1992 or '93.

    It didn't really make too much of an impression on me, though. I dimly remember that is was a very rigidly hierarchical menu-based system, difficult to use if you didn't know where in the hierarchy to look. But that's about all I remember.

    Wikipedia has a good article on Gopher.

    1. Re:Back when I was a Golden Gopher myself by yelvington · · Score: 4, Interesting

      Actually, the hierarchy was NOT rigid. Any node on the tree could point to any Gopher address, so the navigational scheme could be a network and not merely a tree. However, text resources were by definition just text files, and were leaf nodes as a result. They couldn't point anywhere else.

      The big breakthroughs of the Web were the ability to embed a hypertext link at any abitrary location in text, and the ability to embed images (introduced by Mosaic).

      The Gopher model was excellent for a narrowband world. It was a tremendous breakthrough in a darkness where we all had to "just know" Telnet addresses like nyx.du.edu and FTP addresses like tsx-11.mit.edu. It worked great on a plain-text terminal. And it pioneered a lot of things that later made the Web usable, such as link-integrated search engines (Archie, which searched FTP archives, and Veronica, which searched Gopherspace).

      If the cellphone companies weren't so self-destructively larcenous, they would have used Gopher instead of creating that awful WAP/WML mess.

  6. Rutgers University in 1992-94 by Unholy_Kingfish · · Score: 3, Interesting
    My first and last experience was at Rutgers University. At the time Rutgers had lots on info running over Gopher for school stuff. But even then WWW was taking over as THE source for information. Every Comp Sci major (back then it meant programming only) was learning this new language called HTML. We spent more time doing stuff with that than actual work. Not to mention some hacking of the schools network.

    Gopher seemed very antiquated since this new HTML thing allowed you to do the same stuff as Gopher, but also format it, use different text sizes and WOW... pictures. We downloaded this thing called Netscape and opened a text editor and went at it. Anyone at the school that had a "Computer" account could post these so called "web pages" to their personl storage space. It was a very generous amount of space too, 2 MB. We were amazed, we could put almost two 3 1/4 floppies worth of useless stuff there for everyone to see.

    --
    Fear Is the Only God
  7. waaay back... by Balthisar · · Score: 2, Interesting

    in 1996 was the last time I used a gopher server. Also 1996 was the first time I'd used a gopher server. To me (an enlisted soldier in the US Army) the internet was a brand new thing for me and I used everything I could get my hands on. I'd just dumped AOL (yeah, yeah, I was an AOL'er for a year, and that's when they charged per minute) for this internet thing.

    I remember that the gopher program for my Mac Colour Classic had a gopher in a really nifty pair of sunglasses. But it turns out I just didn't gopher very much -- Archie and/or Veronica (am I remembering right?) found everything I needed on FTP, and this is when the web was getting popular -- my first browser was Mosaic.

    All this, and I'm a relative late starter to the internet compared to most of the /. crowd (and an really early adopter in my own crowd).

    --
    --Jim (me)
  8. Two Days Ago :) by HRbnjR · · Score: 2, Interesting

    Some people on a local board I visit were complaining about inflamatory threads being deleted, cencorship, and all that... so I was searching for good info on Canadian Defamation law, and found this:

    gopher://insight.mcmaster.ca/11/org/efc

  9. not quite true by IMSoP · · Score: 2, Interesting

    I was testing out mozilla's gopher:// handler. It actually works :)

    Actually, no it doesn't - try comparing this gopher link with this html proxied version - not the same, I think you'll agree.

  10. I used gopher to get access to telnet by astrashe · · Score: 2, Interesting

    My first internet account was on a unix freenet called Nyx, which was run by a guy named Andrew Burt at Denver University.

    When I first started to use my account, I could dial a local university number, and connect to a telnet prompt. There wasn't even any authentication.

    Eventually they closed that down, but kept access to the library card catalogue open to the public. You could use the card catalog to get to the gopher tree, and from there I could find a telnet link to Nyx.

    I downloaded my first linux distro using kermit through a telnet connection opened via gopher. It was the old MCC distro, which came on a series of floppy disks.

    For me, gopher was more of a means than an end in itself. I didn't spend a lot of time reading stuff on gopher. I did search for telnet links to nyx, which were always moving around (or getting shut down).

    I don't miss gopher at all, because you can think of a gopher menu as a special case of a web page. Every gopher menu can be expressed as a web page, and of course web pages can do lots of stuff that gopher menus can't.

    The first wave of consumer or hobbyist internet use was focused on shell accounts, many of which were on netcom -- you'd dial in with a terminal program, so you didn't have a tcp/ip stack on the computer you were sitting at, and nothing was graphical. Gopher worked well in that world, because it was something that a terminal program could handle.

  11. Usenet and telnet by dougmc · · Score: 2, Interesting
    One example from my campus is the retiring of the newsgroup server and telnet.
    This is a pretty poor example. Usenet has hardly died out -- in fact, I'd guess that more people are using it now than at any other time. The percentage of people online using it is probably lower than it has ever been since it's inception, but with so many people out there, there's still a lot of people using it.

    (Granted, many (most?) are using it for porn and warez, but that was probably true 10 years ago too.)

    As for telnet, ssh is much more like telnet than WWW is like gopher. I doubt many people lament the loss of telnet access (it having been replaced with ssh) ... but going from gopher to the WWW is a very different transition. WWW is everything that gopher wasn't, but gopher had a certain charm that escapes most of the WWW.

    As for when I last used gopher? A few weeks ago, actually. Somebody mentioned it, and I wondered if browsers still supported it (I remember how Mosaic would support it) ... and Mozilla does!

  12. Gopher left a bad taste in my mouth.... by JGski · · Score: 4, Interesting
    The last time was about when gopher+ came out (not sure of the date). The changes to the license pushed me from being a gopher enthusiast into becoming a web enthusiast and gopher-hater. By accident of employment I was on the wrong side of the new UMinn license, despite working on an open-source derivative that was going to be open-source itself.

    I had been working on a C++ version of gopherd and gopher back then. UMinn legal pulled a nasty one on loyal users and contributors: if you were a commerical user or coming from a .com domain, you have to pay us. They claimed to own the protocol so even separate development would cost. It wasn't based on what you did with it or what you added to it like most of today's open source licenses, just the "color" of your domain. Definitely an open license moving to a closed license.

    The commerical-academic-government balkanization was quite strong on the internet back then. No advertising allowed. You had to be careful about regular discussion sometimes (Will this post be seen as an innocent "product support" answer or would it perceived as disallowed commercial speech?). A lot of the nostalgic "gentility" of the old Internet was due to this kind of self-censorship.

    At the time the web seemed more (and unnecessarily) complicated as a technology (remember we had just ftp, telnet, usenet and e-mail to compare it against). However, more importantly, there were no 2nd class citizen clauses on the license unlike gopher+.

    The UMinn license changes pushed me to research web and html further, which I might not have done otherwise - which was financially rewarding a few short years later. I know other folks had a similar reaction and experience. I shutdown all my gopher servers and converted the content to html.

  13. Re:MozillaFirebird 0.7 by SanityInAnarchy · · Score: 2, Interesting

    "just about all modern browsers"

    So I suppose Firebird is out of date? I never suggested it was Mozilla...

    Just because I insult you doesn't mean I'm not thinking, or that you shouldn't.

    --
    Don't thank God, thank a doctor!