Article View: comp.sys.next.misc
Article #1382Re: Cool .dir.tiff/.opendir.tiff (small RTF)
From: Jim De Arras
Date: Sun, 12 Apr 1992 22:43
Date: Sun, 12 Apr 1992 22:43
64 lines
3250 bytes
3250 bytes
In article <275@moene.UUCP> toon@moene.uucp (Toon Moene) writes: >In article <1992Apr11.020819.157@cbnewsl.cb.att.com> coco@ihcoco.att.com >(Felix A. Lugo) writes: >> >> I don't know what you're talking about! 8-) >> >> What I do know, however, is that a bigoted FEW want to >> DICTATE what other people may or may not do in this newsgroup; >> -- AND I'M SICK OF IT! (I should have used RTF for this line). >> >> c.s.n.MISC: Hum, it's name sure fits where such postings >> CAN be made! >> >========================================================================== >= >> Felix A. Lugo >> >> E-Mail: (NeXTmail preferred) Felix_A_Lugo@ATT.COM >> coco@ihcoco.att.com >> AT&T NeXT User Group nug@ihcoco.att.com > > ^^^^ It has been written before: NOTE WHOM WE'RE PAYING TO > FOR THESE RTF/PICTURE/SOUNDS POSTS. > >> HOME NeXTcube home@ihcoco.att.com >> >========================================================================== >= > >Sorry, Felix, but you're not unbiased in this respect. > >-- >Toon Moene (toon@moene.uucp) >Kantershof 269, 1104 GN Amsterdam, The Netherlands >Tel.: + 31 20 6982029; Fax: + 31 20 6003411 >No Disclaimers; a NeXT at home protects against this occupational hazard. > Having been to The Netherlands, and indeed scheduled back there in a month for meetings, I cannot imagine you would have the knowledge to comment on the US phone system, based on the dutch PTT. But, to explain it, AT&T has very little to gain from RTF postings. They may supply some of the backbone circuits, but those are fixed cost. The little additional traffic RTF poses when compared to the alt.gif crowd means that any argument about the additional RTF load requiring additional backbone circuits to be added would be hard to prove. That leaves what I think you were getting at, that it, dial-up time. With the breakup of the Bell system, AT&T gets very little, if indeed any, of the local message unit charges. That would be the bulk of the phone co. portion of uucp access charges. Of the much fewer folks that must dial long distance to connect, even then, regional long distance is, for the most part, charged by the regional operating companies. Of the remain long-distance calls, yes, a percentage will go AT&T. How many get RTF I don't know, but you see we've really trimmed the field. But we also have other long-distance companies, which tend to be cheaper for a uucp style call, so AT&T, and Felix, could hardly care from a monetary return point of view one way or the other about RTF. I do, however, tend to agree with his point of view. This message was posted, and reached the NFS backbone, using no AT&T circuits. Jim De Arras
Technical Details
Message-ID:
<1992Apr12.224335.13606@cube.handheld.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!caen!uvaarpa!cube!newsReferences:
<1992Apr11.020819.157@cbnewsl.cb.att.com> <275@moene.UUCP>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.misc Path: arc1-ca.pugleaf.net!sparky!uunet!caen!uvaarpa!cube!news From: Jim De Arras <jmd@banana.handheld.com> Subject: Re: Cool .dir.tiff/.opendir.tiff (small RTF) Message-ID: <1992Apr12.224335.13606@cube.handheld.com> Sender: news@cube.handheld.com Nntp-Posting-Host: banana.handheld.com Organization: Hand Held Products, Inc. References: <1992Apr11.020819.157@cbnewsl.cb.att.com> <275@moene.UUCP> Date: Sun, 12 Apr 1992 22:43:35 GMT Lines: 66