🚀 go-pugleaf

lyndon@cs.athabascau.ca writes:
>How do you plan to coerce the majority of BITNET sites...to use async proto-
>col, uucp, ASCII, etc...and how do you plan to identify BITNET sites?  
>Summary, not verbatim.
I find that your question contains incorrect assumptions, starting with the
use of the word 'coerce', and continuing through to the assumption that the
viable way to identify a BITNET site is through a list forwarded from 
BITNET.  As for access, implement it--or don't--any way you like; it is self-
evident from the continued existence of internetwork mail and previous file
transfer that neither data nor protocol is untranslatable.  I am unable to 
discern precisely why there is no chance that I'd be handling your traffic, 
as I do not think it beyond the bound of reason to suppose that I might be
archiving something of interest to some user on BITNET.  You are of course
at liberty to use your connections any way you wish; so am I, and I do not
wish to forward information to someone who refuses to return the courtesy.
I suggested dialup as a possible method of bypassing an uncooperative 
network in the event that a BITNET site chose not to isolate itself from
the rest of the user community; conceivably there are better ways, and if so,
I would certainly withdraw my suggestion in their favor.
	I am extremely sorry, but I do not intend to take further part in  
this discussion because I am not sure that the intent of your question was
actually to elicit information.  If I have misjudged your intention, I beg
your pardon.