This page will discuss the main open peer to peer (p2p) networks the OTR collector might like. I do not discuss proprietary networks like Kazaa, etc.
gnutella-technology networks
gnutella-technology networks (GTNs) are systems where users connect to each other and searches are passed around from node to node. Since the software functions as both client and server it is sometimes called a "servent" or "servant". Transfers are directly peer to peer. The original client was called Gnutella, hence the name of the network technology.
I recommend the GNUcleus gnutella servent.
Upside: unable to be shut down from any central location. All file types.
Downside: uses bandwidth even when not actively up/downloading files, since all searches are passed from client to client.
napster-technology networks (NTNs) are systems where users all connect through a centralized server or collection of servers. Searches happen on the server and transfers are directly peer to peer.
I recommend the audioGnome napster client.
Upside: rapid searching due to central servers, uses little bandwidth unless you are up/downloading
Downside: theoretically mp3/wma files only. Centralized servers are susceptible to legal action.
Napster, in current usage, has several meanings.
Napster, the technology invented by Shawn Fanning.
Napster, Shawn's nickname
Napster, the company organized around the technology
Napster, a set of Napster-technology networks (NTNs hereafter). There are non-Napster NTN clients (AudioGnome, etc) and non-Napster NTN servers (OpenNap, usually) and networks. They look and act like Napster, but aren't. They are Napster clones. One such clone for OTR is OTRnap.
There is a wealth of OTR on p2p, if you know where (or how) to look. Here is a process to help you get started. For purposes of our discussion we will assume I am trying to find the following file:
CBS Radio Mystery Theater #2, The Return of the Morsebys. Jan 7, 1974.
learn how P2Ps find files
NTN clients connect to NTN servers, and tell the servers what files they have to share. This may or may not include path information (folder names), depending on the client and server. This information is stored in a database on the server. When another client does a search, the search keywords are compared to the server's database; matches, if any, are returned. When a user finds a file s/he wants and clicks "Download" in the client software, the client learns from the server the IP address of the user with the file and contacts them directly. (It works differently if the file is on a firewalled connection).
What is important to understand here is that your keyword search will be run on file (and perhaps path) names stored at the server in question. This means you have to guess the path/filename of the file you want to find.
gnutella clients talk to each other, passing around search terms and hits. Searching usually takes a bit longer on gnutella nets.
Start out with broad terms - your first crack at finding a file will probably be a wide net: 'cbs radio mystery theater', 'radio mystery theater', 'mystery theater', 'rmt', 'cbsrmt'. You will find that filenames will usually have similar naming conventions. Remember the important ones. You might even want to search for "otr" just to see how much is out there...
Narrow it down - once you figure out common naming conventions (like the pro-word 'cbsrmt'), you can start narrowing down your search. The trick is to find a unique string that is likely to be in the filename. Let's discuss the ones in our example:
#2 - could be 2, which would end up with lots of false positives. Could be 002 or more likely 0002, since there are 1400 shows in the series.
Return - good one. Probably not too many shows with 'return' in the title.
Moresbys - problematic. Could be typo-ed too many ways in filenames, particularly if someone had not consulted the log. Moresbies, Moresbees. The log at Bob Cook's site had the file incorrectly listed as "moresby's" which would might gum up your search.
1974 - could be found as 1974 or 74. Some clients/servers do not seem to search on numbers consistently. Note that a search on the year 74 (1974) would be more useful than a search on the year 1930 (30) because 30 can also refer to a date, resulting in many false positives.
datestring - 740107 or 010774.
Re-run the query - if you don't find it, try again on a regular basis. Some clients, like audioGnome, will keep all your searches in a dropdown for easy access later. Remember that NTN file listings are very fluid, and change as folks sign on and off.
Share rare shows - when you do find that rare show, please check it for errors and completeness and share it whenever you are online. The popular stuff isn't so important, but the rare stuff really needs our help.
sharing your OTR
One nice thing about sharing OTR is that you're not part of the legal problems affecting Napster right now. No one is going
to get banned for sharing public domain OTR.
Here are some thoughts about sharing:
if nothing else, share your rare stuff and your original encodes.
don't share your download directory. Check all your files manually (at least beginning and end) for completeness and quality before moving to a shared directory.
if you are concerned about bandwidth, use one of the NTN clients (like audioGnome, etc) that will let you control bandwidth usage. You can control number of downloaders, bandwidth per download, number of concurrent downloads per person, etc.
to save discspace, you can burn a cd-r of rare/favorite files and share them from the cd drive.
if you have a spare machine and a steady connection, you may want to consider making it a standalone p2p client box. That way all the action is off your workstation.
the mousepad