The content of this message has been quite adequately rebuted in
detail; here's a few more points:

   Date: Tue, 4 Jun 96 01:41:25 -0600
   From: Travis Butler <tbutler@tfs.net>

   [...] There is a problem, I'd say, and something needs to be 
   worked out to fix it -- but I don't think any of us have a right to flame 
   Megazone without knowing the circumstances.

The circumstances are utterly irrelevant.

If you step up to a service responsibility that's big in scale (or
very important), it's your responsibility to see that service is
maintained in foreseeable situations, like vacations.  You don't see
newspapers shutting down when the editor in chief goes on vacation, do
you?

I'll reiterate: Megazone has a straightforward and crystal clear set
of rules for running raac; it would be simple in principle for him
to find a few trustworthy people to cover the raac posting duties
while he's unavailable, leaving offical integration into the archive
for his return (a "New" directory would suffice in the meanwhile).

He has had multiple offers of help, and apparently turned them all
down; it's clear that timeliness of service is pretty low on his list
of priorities, although going beyond that is supposition.

A suggestion; if service continues to be poor during the summer, in
the fall when everyone returns to the net, the actual fanfic authors
on the list might want to put together a petition asking Megazone
impliment the above (with some of us being prepared to completely
assume responsibility in case he "decides to take his marbles home" as
one of us put it).

   I personally would go further; I wouldn't flame him without
   evidence of deliberate, vindictive intent, and probably not even
   then.

   Besides, one almost always gets better results from understanding 
   sympathy (as long as it's honest!) than from flaming tirades.

Echoing the target of your message, you would do well to follow your
own advice, seeing as how you are the person who escalated this topic
beyond frustration, to flames.

					- Harold