Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrlnk!ncrcce!pasek
From: pasek@ncrcce.StPaul.NCR.COM (Michael A. Pasek)
Newsgroups: comp.sys.mac
Subject: Re: comp.mac.binaries
Summary: Give the moderator a break...
Keywords: binaries
Message-ID: <1856@ncrcce.StPaul.NCR.COM>
Date: 24 Jan 90 18:49:43 GMT
Expires: 29 Jan 90 05:00:00 GMT
References: <3514@husc6.harvard.edu> <126900136@p.cs.uiuc.edu> <1110@urbana.mcd.mot.com> <2848@cerberus.oakhill.UUCP> <1990Jan22.185856.6930@ultra.com>
Reply-To: pasek@c10sd3.StPaul.NCR.COM (M. A. Pasek
Followup-To: comp.sys.mac
Distribution: na
Organization: NCR Comten, Inc.
Lines: 18

In article <1990Jan22.185856.6930@ultra.com> casey@ultra.com (Casey Cox) writes:
>My question is: Why does it take so long to get things thru comp.mac.binaries?
>What is this "queue of programs waiting to be posted" nonsense?  I understand
>that there is some poor moderator out there processing submisstions, but how
>long should it take to make a decision to post or not to post??????

I think one of the reasons it takes so long is that the moderator has other
things to do (I doubt if this "job" carries any financial incentives with it--
perhaps Casey would like to take over ?).  I think (hope) that another 
reason it takes so long is that the moderator does some verification that
the program works (on various machines/configurations), and (most important),
has no DISASTROUS effects (e.g., trashing disks, virii, etc.).  While I
agree that comp.binaries.mac is not the place for HUGE crippleware posts,
there's no need to flame the moderator.

M. A. Pasek          Switching Software Development         NCR Comten, Inc.
(612) 638-7668        CNG-er-PU4-er-MNI Development       2700 N. Snelling Ave.
pasek@c10sd3.StPaul.NCR.COM                               Roseville, MN  55113