TASK OUTLINE
The task requirement was to use the Telnet application to access the Curtin Library server, search and retrieve information . The objective was to experience (or re-experience) a process that is now considered simple and commonplace using the web, via an earlier mechanism.
PROCESS
Although it all felt vaguely familar, I can’t recall having used Telnet before, and certainly never via the Mac I now use. As a result, the task proved tricky to initiate compared with the search and retrieve ‘experience’ I have become accustomed to in recent years via the web.
The initial problem was figuring out where the Telnet client was located in my system, how to access it and how to use it. Most of the information I’d read pertained to PCs at that stage and didn’t apply. However, using a combination of Mac Help and Google, I soon discover that the Telnet client exists as a part of the Terminal application.
The initial screen within Terminal is shown below. I could not see what the next step should be and in particular where the Telnet ‘part’ could be located. Initilly I tried typing the Curtin Address into the screen below, thinking that it could be a command prompt designed for that purpose. When that didn’t work I opted for the help menu in Telnet.
I discover in help that connecting remotely in Terminal required the user to: ’Choose Shell > Remote Connection’ (as shown below)
Although I now felt I could progress with the task from here, not knowing what ‘Shell’ even meant was bugging me to the point where I ended up off on a tangent finding out (sometimes it takes me a loooong time to get to the end of a task because of this irksome trait). For the interested ‘Shells 101′. The next step was to select the Telnet option, add the address using the reasonably (providing one is quite computer literate) straightforward menu screen shown below, and click Connect
Oh this is easy I thought! that is until I got to the next screen. What terminal am I using? Hmm a good question, but one I do not know the answer to….
This time I just guessed, chose W and hoped for the best. It seemed to work ok as the next screen looked like what I was after.
RESULT! I find the search menu easy enough to work out, and minutes later I have an email from Curtin Library with the information I was seeking.
SUMMARY & OBSERVATIONS
In general, I found this task reasonably easy to execute, although that was only the case once I actually got into Telnet… This lead me to thinking about how far we have come in the past 10 years in terms of user interfaces. More specifically the usability and intuitive design of modern interfaces. Telnet naturally compares unfavourably with modern web interfaces in this respect. Essentially Telnet does what it is designed to do effectively, however user skill and knowledge must be applied in order to achieve a result.
As for the Telnet user experience, it reminded me of a Unix database I used during the late 90’s in my first job. Generally it was stable, secure and even easy enough to use and navigate, but only once you’d rote learned a series of codes and commands and become accustomed to the logic of navigation.
As for the Telnet user experience, it reminded me of a Unix database I used during the late 90’s in my first job. Generally it was stable, secure and even easy enough to use and navigate, but only once you’d rote learned a series of codes and commands and become accustomed to the logic of navigation.
Although the lack of graphics and user features in Telnet definitely made for a rudimentary and basic feeling user experience, the main drawback to Telnet – is simply its relatively low usability when approached by a wide population. Telnet requires its users to first ‘learn’ to interact with the system on its terms before information can be successfully obtained. The command entry requirement involves the user (albeit in a very minor way) in the program’s process…. this is certainly not for everyone, although I surmised that those with programming experience or used to logical sequences/process would have an easier time than others. Using Telnet highlights the leaps and bounds that have been made broadly in terms of user interfaces in order to bring down barriers to the point where a wider population with minimal (if any) computer literacy can use the Internet to find information, communicate and even upload information. Without this, it is difficult to imagine Internet 2.0.
