Source: Computer Shopper, March 1993 v13 n3 p780(1). Title: Unix notes: let gopher get it. (the gopher utility program for using the Internet) (Tech Section) (Tutorial) Author: Steven J. Vaughan-Nichols Abstract: Gopher is a general-purpose information utility program for using the Internet. Whereas the archie information source relies on a centralized archie database of ftp-able files, gopher does not rely on any specific data collection. Gopher is able to find information without users having to know IP addresses, file formats or domain names, and it does not require knowledge of Unix. After installing the gopher client on the user's system, typing 'gopher' at the command prompt presents a set of menus. The gopher server handles finding the location of the information and logging onto that system; each gopher client has a precoded gopher server it looks to for information, but this can be changed to access the closest available gopher server. Users are presented with two types of choices: resources, which are the actual sources of information, and directories, which lead to submenus that narrow the choices until the appropriate resource is reached. Products: Internet Gopher (Search software) - Design and construction SIC code: 7372 Electronic Collection: A13399722 RN: A13399722 Full Text COPYRIGHT 1993 ZDNet Let's face it, getting the most out of the Internet isn't easy. Even archie, described in my last visit, only helps with one specific area of net use, finding and "ftping" files. Probably more than a few of you have been saying, "The net is neat, but why does it have to be so hard?" Well, these days, with the right software, it doesn't have to be so hard. There are two user-friendly programs that makes using the Internet's resources easier than ever before: gopher and wais. Before this dynamic duo showed up, some of the net's most valuable resources were only available to a lucky few in the know. The most important of these resources are the online databases. These systems provide public access to everything from library catalogs to technical documentation collections. Unfortunately, few people knew how to access these databases. Now, with gopher at your side, you can liberate this information for your own uses. GOPHER Gopher and wais may sound like Ren and Stimpy, but they're anything but cartoons. Unlike the other tools I've been looking at, ftp and archie, gopher is a general-purpose information tool. Gopher builds on the foundation of ftp, archie, and other information sources to erect an easy-to-use, menu-driven interface to the net's file and informational resources. Unlike archie, which relies on a centralized archie database of ftp-able files, gopher doesn't rely on any particular data collection. To use the analogy of a library, archie is like a card catalog dedicated to publicly available files. Gopher, on the other hand, is like a librarian. Gopher doesn't know where a particular item is, but it does know where to find out where the information is hiding. The best thing about gopher is that you don't have to have a clue about where some file or bit of information is. IP addresses, file formats, domain names--forget 'em: With gopher, you don't need to know Unix esoterica. Gopher does the dirty work; all you have to do is pose the questions. GETTING A GOPHER To get gopher started, you should have a gopher client on your system. If you don't, you can telnet your way to a site with a publicly accessible gopher client the same way you can access archie. You shouldn't have to do this, however. Gopher client programs are free and come in makes and models for almost every architecture and operating system under the sun. While the Unix character-based interface is the most common front end to gopher, you can also get a HyperCard-style gopher for the Macintosh and a DOS-character-interface-based subspecies for PCs. You can get the right one for your system by using archie to find a nearby site with ftp-able gopher files. If all else fails, you can always find the gopher clients at the site: boom - box.micro.umn.edu in the pub/gopher directory. Always look for a closer site first--everyone who is a "net's" expert knows about boom-box, and that site can be very busy. Once you've installed the program, usually a simple task (you will require system administrator privileges on Unix systems), you type gopher at your command prompt. You will be presented with a set of menus. Proceed by selecting the choice that looks like the best path to your informational destination. You could, for instance, decide that you want to find a library with a copy of the newest Tom Clancy thriller. In the pre-gopher days, you'd do this by telneting to every computerized library catalog you could think of. And who really knows all the IP addresses or domain names for automated card catalogs? Even if you found your library and its access point, you would still be faced with the problem of how to log onto the system. Some just let you right in, some require a user ID of "guest" or "anonymous," and so on. Assuming you made it that far, you would still have to figure out each system's particular idiosyncrasies. It's no wonder that, until recently, Internet information access has been a black art practiced only by net gurus. GO-FER IT With gopher, however, the gopher server takes care of all this. Your client gopher starts looking for the information. It does this by first checking for local resources, usually a gopher server, or telnets to a preset gopher service. Gopher clients come with a precoded gopher server they look to for information, but this can, and should be, changed to access the closest available gopher server. The server, presented with your request, then tries to figure out where to find the information. All you know, sitting at your desk, is that a few seconds after you start your inquiry, gopher has presented you with menu choices that take you closer to your destination. These choices come in two forms: resources and directories. A directory, marked with a "/" at the end of its menu item, indicates that choosing this item will lead you to a submenu. Resources are--as the name indicates--actual sources of information. From the menus, you proceed to narrow down your choices until you can reach an appropriate resource. In our search for our Clancy high-tech shoot-'em-up, for example, we can probably live without looking into the card catalogs of libraries thousands of miles away. Eventually, you end up with what you and gopher agree is probably a system or program that can supply you with the information or file you need. At this point, you instruct the gopher to go-fer it. THE GOPHER SHIELD When you access a resource, gopher takes over the job of logging in to the computer and service. Gopher also shields you from the local system. No matter what you're logged into, you use gopher's search interface, not the remote systems. This has one great advantage: You never have to learn the ins and outs of a database you may only use once. There are two mirror image problems to gopher's approach, however. The first is that while gopher can perform fairly complicated searches, you may not know if the software that the gopher is talking to can handle it. Archie, for example, can only search on a single word. Or you could try searching for, say, "386DX and Unix." Some systems take that to mean you want to know about books or articles which contain both the words "386DX" and "Unix." Others assume you really want the phrase "386DX and Unix." With gopher in the way, you'll only know that your searches are going wrong. The flipside to this is that gopher defaults to the lowest common denominator searching. The resource you're accessing may be capable of very precise searches, but you'll be limited to gopher's search capacities. Gopher, for instance, can't tell the difference between lowercase and uppercase. This may not be a big deal if you're only occasionally on a data hunt, but big-time information hunters will want to throw gopher out the window--at least until they recall how much work searching for information without gopher is. Another thing you should keep in mind with gopher is that sometimes it may dig up an information resource for you that you can't access. The most common example of this is the news services. The UPI news feed is available, for example, on many academic sites, but it's inaccessible from most commercial sites--no matter what the gopher menu says. NOT ALL GOPHERS ARE EQUAL Another interesting point is that not all gopher servers are the same. Some servers may be much stronger in certain areas than they are in others. That's because gopher servers tend to be best connected to local resources. The original gopher server at the University of Minnesota, to no surprise, is filled with information resources from that school. One of the most interesting things about gopher, however, is that you're not limited to a single server. You can use gopher to hunt for other gopher servers that might give you access to information that's more your speed. Flaws and all, you'll never mistake gopher for such powerful single-purpose online information retrieval engines as ZiffNet's Computer Library, but gopher does have its good points. Because gopher brings the almost limitless information resources to your reach, it is an invaluable tool for any Internet explorer. Gopher is not alone in making the Internet a better place for information hunters. Next time around, I'll take a look at wais and, still making the transition from experimental to essential, web. -- End -- .