🚀 go-pugleaf

In article <1992Apr10.160856.2790@cs.yale.edu> nathan@laplace.biology.yale.edu (Nathan F. Janette) writes:
> In article <1992Apr9.225405.15278@cbnewsl.cb.att.com> coco@ihcoco.att.com  
> (Felix A. Lugo) writes:
> > In article <1992Apr9.200738.18240@cs.yale.edu>  
> nathan@laplace.biology.yale.edu writes:
> > [chomp]
> > 	I love RTF-NewsGrazer ... Keep-em coming gentry!
> 
> NOT!
> 
> This is not the correct newsgroup for such things, and you
> know it. Please stop trying to provoke a flame war, which
> you will most *surely* do.
> [chomp]
> nathan@laplace.biology.yale.edu (NeXT)

God! This really pisses me off! I have a SLIP connected NeXT 
at home and a variety of non-NeXTs at work. I read the bulk 
of my netnews at work and I LIKE RTF posts!

- Just because I can't see the RTF doesn't mean it
  shouldn't be posted. I'll go to the trouble if I'm that
  interested in the subject. If that's not an option, write
  a program that'll read RTF on your hardware and people
  will thank you for it! 
- I read netnews at home over a slow slip connection so
  don't complain about bandwidth. Half the _textual_
  stuff is worth less! 
- I pay for a Compuserve account and read/download lots of
  things that don't work out to be worth their cost. I'm
  still happy that the poster took the trouble to make it
  available even if it's not right for me. 

On the other hand, RTF posts are almost always clearer in the 
message that they are trying to convey. A separate RTF newsgroup 
won't work in that some replies to textual messages are better 
in RTF (push this button in Icon...). Putting a pointer in a textual 
reply to see the rtf group will be a pain.

This thread is one of the few that _would_ work in an RTF newsgroup 
and yes, I read (and saved) part of it at work.

Phew... Better....
Paul Verket (NeXTmail ok -- even to this nonNeXT address!)