BITNET Relay

<h2 id="background">Background</h2>
<p>Before BITNET Relay was implemented, any form of communication over BITNET required identifying the remote user and host.
</p><p>Relay ran on a special <a href="/facts/User_identifier/PurxNtA5">ID</a> using several BITNET hosts. To use it, a message was sent to a user ID called RELAY. The Relay program running on that user ID would then provide multi-user chat functions, primarily in the form of "channels" (<a href="/facts/Chat_room/QbFjlYQU">chat rooms</a>). The message could contain either a command for Relay (preceded by the popular "/" slash character command prefix, still in use today), or a message at the remote host (typically a <a href="/facts/Mainframe_computer/nrBR6rWa">mainframe computer</a>).
</p><p>Computers connected to BITNET were generally located at universities and government agencies, due to limited access to computer network bandwidth. It was not uncommon for a university's entire network connection to run over a single <a href="/facts/Leased_line/JzGppCIP">leased telephone line</a> or even a 4800 baud <a href="/facts/Dial-up/gfhNU9s3">dial-up</a> connection. Thus using scarce computing and network resources for "frivolous" purposes, such as chat, was often discouraged.
</p>
<h2 id="popularity">Popularity</h2>
<p>One of the reasons Relay gained acceptance was that its system of peer servers decreased the network bandwidth consumed by group chat, due to no longer having to send multiple copies of the same message individually to each server. Because of this efficiency and the limited bandwidth at the time, users were often not allowed to use or develop alternate chat systems. Experimental chats like <i>Galaxy Network</i> and <i>VM/Shell</i> were asked to shut down before they achieved noteworthy success.
</p><p>Bitnet Relay gained popularity in the late 1980s when Valdis Kletnieks at <a href="/facts/Virginia_Tech/5nNYd0ur">Virginia Tech</a> created a <a href="/facts/Pascal_(programming_language)/b3yvp8bF">Pascal</a> version that consumed far less <a href="/facts/CPU_time/BhzkBzFl">CPU time</a>, and again in the early 1990s when Smart Relay improved handling of message delivery.
</p><p>Though Jeff Kell himself had made observations about the possible demise of BITNET Relay, only <a href="/facts/TCP%2fIP/KNkxtSpw">TCP/IP</a> and the <a href="/facts/Internet/Xw1rVvJU">Internet</a> brought about the end of BITNET and Relay. <a href="/facts/Jarkko_Oikarinen/PgQzxJRE">Jarkko Oikarinen</a>, the creator of <a href="/facts/Internet_Relay_Chat/oDr3VN9q">Internet Relay Chat</a>, says that he was inspired by BITNET Relay<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a>
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Relay_(disambiguation)/5rlqIm0p">Relay (disambiguation)</a></li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="http://web.inter.nl.net/users/fred/relay/">Historical Relay Pages</a></li>
<li><a href="https://web.archive.org/web/20131203015800/http://www.utc.edu/information-technology/profiles/qnh116.php">Jeff Kell profile</a> at <a href="/facts/University_of_Tennessee_Chattanooga/f11XWFvq">University of Tennessee Chattanooga</a> website.</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Kell, Jeff (1987). "Excerpt from "RELAY: Past, Present, and Future"". <a href="http://web.inter.nl.net/users/fred/relay/relhis.html" target="_blank">http://web.inter.nl.net/users/fred/relay/relhis.html</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Oikarinen, Jarkko. "Founding IRC". <a href="/wiki/Jarkko_Oikarinen" target="_blank">/wiki/Jarkko_Oikarinen</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
</ol>

BITNET Relay open-in-new

BITNET Relay