Path: utzoo!attcan!uunet!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: rmadison@euler.berkeley.edu (Linc Madison)
Newsgroups: comp.dcom.telecom
Subject: Re: Alert: AT&T May Consider Removing TDD Long Distance Discount
Message-ID: <8339@accuvax.nwu.edu>
Date: 28 May 90 10:59:37 GMT
Sender: news@accuvax.nwu.edu
Organization: University of California, Berkeley
Lines: 17
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 391, Message 3 of 12


Having made one TDD-to-TDD call and several TDD-relay calls, I can
verify that even with fast typists, TDD calls have much slower
throughput than voice.  Speaking, I can about keep pace with text
rolling across my CRT at 1200 bps and can with a little effort almost
keep up with 2400 bps.  Someone quoted TDD standards as being 45 bps;
even if it's old TTY at 110 bps, it's still slow.  My roommate who
heard me on a relay call once asked,
"why...........were............you.............talking..........
 .......so..........slowly.....?"

(BTW, in case you're curious, I can type about 120 wpm, which is well
into the range of professional typists, and TDD was still painfully slow.
For a comparison, try a "talk" connection on UNIX, and then halve it.)


Linc Madison   =   rmadison@euler.berkeley.edu