🚀 go-pugleaf

In article <1992Apr14.190134.1216@cs.yale.edu>
nathan@laplace.biology.yale.edu writes:

>the obvious new newsgroup
>would be "comp.sys.next.rightbrain.rtf", which I'm
>sure would come out in every monthly top-ten USENET
>volume listing, second only to the SEF email bounces
>of the same posts.

>"It's a joke, son."

I don't think I'm humor impaired, not the least.
It's too dorky to be funny.

-- 
Jess Anderson <> Madison Academic Computing Center <> University of Wisconsin
Internet: anderson@macc.wisc.edu <-best, UUCP:{}!uwvax!macc.wisc.edu!anderson
NeXTmail w/attachments: anderson@yak.macc.wisc.edu  Bitnet: anderson@wiscmacc
Room 3130 <> 1210 West Dayton Street / Madison WI 53706 <> Phone 608/262-5888

Nathan F. Janette writes [and GR reads, despite kill file]:

> Since Jack Reynolds has just joined Glenn Reid at
> RightBrain as VP of sales, the obvious new newsgroup
> would be "comp.sys.next.rightbrain.rtf", which I'm
> sure would come out in every monthly top-ten USENET
> volume listing, second only to the SEF email bounces
> of the same posts.

No, you've got it backwards.  Now that Jack is at RightBrain,
the overall frequency of RTF posts will DECREASE.  We won't
both need to post the same thing, after all :-)

But I like the idea of comp.sys.next.rightbrain.  I'll vote
for it :-)

By the way, I don't foresee any increase/decrease in RTF posting
as a result of the vote against the *.rtf newsgroup.  It mainly
indicates that it's the wrong solution to the problem.

Despite being an avid "multi-media" proponent (not necessarily
RTF, but at least a step up from ASCII) I'm in favor of a mechanism
that permits people who aren't interested in it to restrict its
distribution.  That makes sense.  However, the negative vote
shows an underlying problem that is that postings in different
MEDIA do not necessarily reflect different SUBJECT matter, and
the current newsgroup hierarchies are split by subject.

My feeling is that, in 1 to 4 years, the entire net will migrate
toward richer postings, and the solution will not be to proliferate
*.richtext newsgroups.  The solution will be to tag messages with
an ID that shows that they are "multi-media" and to permit the
"multi" part to be stripped under software control, leaving the ASCII
portion intact.  Then the backbones that do this stripping will fall
into disuse, because everybody will love the typographically rich
formats, and we'll all just live with the bandwith issues.  As it is,
the bandwidth has mostly suffered by the proliferation of people who
read the net, not from software.

--
 Glenn Reid        		NeXTmail: glenn@rightbrain.com
 RightBrain Software		415-326-2974 (NeXTfax 326-2977)
 Palo Alto, California		Font Hotline: 800-525-FONT