🚀 go-pugleaf

In article <466i1o$e9i@newsbf02.news.aol.com>,
Cyronwode <cyronwode@aol.com> wrote:
>bei@io.com (Bob Izenberg) wrote: 
>
>> Now, if you were a system administrator, and you had to
>> choose whether to make a service available to the Net at
>> large, and to commit your time to maintain it, how would
>> the events that we're discussing affect your decision?
>
>Good question. My answer is in 5 stages of increasing limitation. It does
>not include shutting down the gateway. 

Since you are not a system administrator, and have no idea of what being
one involves, your answers aren't based on a concept of what it
involved.

>(1) 
>If my system had the capacity to handle the current volume of
>mail-to-usenet traffic from Compuserve, Prodigy, Netcom, Delphi and the
>like, i think i would have accepted the offender's apology, talked things
>over with AOL, and gone on from there. 

Of course, your preferred course of action would be "kiss and make up".
I think there is a slight bit of bias here.

>(Incidentally, i got a message from Zac at AOL the day before the gateway
>was closed saying that the newsgroup admin (Bob) was on vacation but that

Newsgroup Admin Bob? Which newsgroup is this Bob the admin of? 

>(2)
>If i felt that my gateway was overtaxed with messages from .com users in
>general, i would have written a bounced mail message and henceforward

Wait a minute. The question was about "the events we are discussing".
That isn't the "overtaxing" of a gateway by users, it is YOUR ranting
and threats.

You are a system admin. You have a shitload of things to do. Things that
you are actually getting paid to do, and that must be done so that the
people who pay you can continue to use the system. You have no time to
write gratuitous code. Solution 2 is ruled out.

>(3)
>If i felt i was still doing too much work, i would have written a bounced

You are a system admin. You have a shitload of things to do. Things that
you are actually getting paid to do, and that must be done so that the
people who pay you can continue to use the system. You have no time to
write gratuitous code. Solution 3 is ruled out.

>(4)
>If i felt i was still doing too much work, i would have written a bounced
>mail message and henceforward would have *politely* bounced ALL messages

You are a system admin. You have a shitload of things to do. Things that
you are actually getting paid to do, and that must be done so that the
people who pay you can continue to use the system. You have no time to
write gratuitous code. Solution 4 is ruled out.

>(5) 
>If i felt i was still doing too much work, i would have written a bounced
>mail message and henceforward would have *politely* bounced ALL messages

You are a system admin. You have a shitload of things to do. Things that
you are actually getting paid to do, and that must be done so that the
people who pay you can continue to use the system. You have no time to
write gratuitous code. Solution 5 is ruled out.

Solution 6:

Some idiot is making noises about complaining about what you have done
on your own time as a benfit for others. She is demanding to know the
sorts of things that people use in formal complaints to bosses and
Deans and people-in-charge. She is making noises that she thinks she has
a Right to your Services because She has paid taxes and there is some
Tax Money involved in paying for the hardware. You get fed up with it
and shut down the service because you don't want to have to worry about
some idiot getting you in trouble with your boss.

As a system admin, I feel safe in saying that solution 6 will be the
normal solution to people like you. I know that, should you decide to
target any of the net-things I do, it is the solution I would take.