The bad part of writing about
telnet — which is to say, the difficult part — is showing it in action.
As I understand it,
telnet just gives you a tool for accessing the telnet protocol, probably in the same way that a browser is a tool for accessing http (and other) content. So once it’s up and running, there’s not much of
telnet itself to see.
The good part is, if you have telnet access and a live line to the Internet, you will never, ever lack for things to do.
For every graphical game that requires a rat’s nest of dependencies and specific hardware support and only coughs up a generic shoot-em-up experience, there are probably 10 well written, well developed text-only games that only require an active connection and an 80×24 terminal space.
A thousand themes, a thousand environments and a thousand worlds to explore, in every variation imaginable, and no more hardware requirements than what you can scrape up with a leftover 133Mhz laptop and a lousy PCMCIA network card.
So in the end, the magic of
telnet is not what it does, but what it gives you access to.
Perhaps that’s a lesson for elsewhere in life as well. 😉