rmarks@KSP.Unisys.COM (Richard Marks) (02/06/90)
I do not see anyone volunteering to moderate comp.binaries.ibm.pc. Thus I propose that the group become un-moderated. It used to be un-moderated and seemed to work well. The major problems with it being un-moderated was that some software came thru un-tested. (Twice I posted something only to re-post it within a week with bugs fixed.) A secondary problem is viruses. But the stuff on SIMTEL is also un-moderated - Keith does not test every package. Regards, Richard Marks rmarks@KSP.unisys.COM
w8sdz@smoke.BRL.MIL (Keith Petersen) (02/22/90)
rmarks@KSP.Unisys.COM (Richard Marks) writes: >A secondary problem is viruses. But the stuff on SIMTEL is also >un-moderated - Keith does not test every package. The file uploads to SIMTEL20 *are* moderated. There is no way FTP users can delete, modify, replace, or otherwise alter the files. They do not have write privs in the public area. We have a special upload directory for FTP file submissions. All files are screened with a virus scanning program. Keith -- Keith Petersen Maintainer of SIMTEL20's CP/M, MSDOS, & MISC archives [IP address 26.2.0.74] Internet: w8sdz@WSMR-SIMTEL20.Army.Mil, w8sdz@brl.arpa BITNET: w8sdz@NDSUVM1 Uucp: {ames,decwrl,harvard,rutgers,ucbvax,uunet}!wsmr-simtel20.army.mil!w8sdz
hartung@amos.ucsd.edu.ling.ucsd.edu (Jeff Hartung) (02/23/90)
In article <739@bbking.KSP.Unisys.COM> rmarks@KSP.Unisys.COM (Richard Marks) writes: >I do not see anyone volunteering to moderate comp.binaries.ibm.pc. > >Thus I propose that the group become un-moderated. It used to >be un-moderated and seemed to work well. > >The major problems with it being un-moderated was that some >software came thru un-tested. (Twice I posted something only >to re-post it within a week with bugs fixed.) > >A secondary problem is viruses. But the stuff on SIMTEL is also >un-moderated - Keith does not test every package. The third problem is copyrighted programs being posted. The forth problem is duplicate postings and unnecessary reposts, which eventually cause the group to be excluded from many systems. The fifth problem is that stuff posted just plain doesn't work often. The sixth problem is that, due to 1-5 above (at least) c.b.i.p was almost SHUT DOWN when it was unmoderated. The seventh problem is that, in spite of the fact that most people seem to reject the un-moderate suggestions (that come back like weeds every few weeks) when they come up, someone has to go and start this stupid topic up again just as it dies down from the last round. :-) The eighth problem is that we *have* a moderator, and have received several postings in the last week. Where were YOU, Richard? --Jeff Hartung-- Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!... ARPA - hartung@amos.ucsd.edu UUCP - ucsd!amos.ucsd.edu!hartung BITNET - hartung%amos.ucsd.edu@sds.sdsc.edu
dhw@itivax.iti.org (David H. West) (02/23/90)
In article <7882@sdcsvax.UCSD.Edu> hartung@amos.ucsd.edu.UUCP (Jeff Hartung) writes: |In article <739@bbking.KSP.Unisys.COM> rmarks@KSP.Unisys.COM (Richard Marks) writes: |>Thus I propose that the group become un-moderated. It used to |The eighth problem is that we *have* a moderator, and have received several |postings in the last week. Where were YOU, Richard? From the header of Richard's article: Message-ID: <739@bbking.KSP.Unisys.COM> Date: 6 Feb 90 14:39:38 GMT ^^^^^^^^ Please look before you flame, Jeff.
ts@uwasa.fi (Timo Salmi LASK) (02/24/90)
In article <7882@sdcsvax.UCSD.Edu> hartung@amos.ucsd.edu.UUCP (Jeff Hartung) writes: >The eighth problem is that we *have* a moderator, and have received several >postings in the last week. Where were YOU, Richard? Although this is not quite my business, did you look at the date of the posting you referred to? I think that some site fed three-weeks old messages to the net. If true, this causes unnecessary confusion (not that I know what necessary confusion would be :-). ................................................................... Prof. Timo Salmi (Moderating at anon. ftp site 128.214.12.3) School of Business Studies, University of Vaasa, SF-65101, Finland Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun
hartung@amos.ucsd.edu.ling.ucsd.edu (Jeff Hartung) (02/24/90)
<|In article <739@bbking.KSP.Unisys.COM> rmarks@KSP.Unisys.COM (Richard Marks) writes: <|>Thus I propose that the group become un-moderated. It used to <In article <7882@sdcsvax.UCSD.Edu> hartung@amos.ucsd.edu.UUCP (Jeff Hartung) writes: < <|The eighth problem is that we *have* a moderator, and have received several <|postings in the last week. Where were YOU, Richard? In article <4991@itivax.iti.org> dhw@itivax.UUCP (David H. West) writes: < <From the header of Richard's article: < Message-ID: <739@bbking.KSP.Unisys.COM> < Date: 6 Feb 90 14:39:38 GMT < ^^^^^^^^ <Please look before you flame, Jeff. My apologies, however, my points are still valid, and the redundant demands to create an un-moderated binaries group *do* seem to crop up again, and again, (and again ...) --Jeff Hartung-- Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!... ARPA - hartung@amos.ucsd.edu UUCP - ucsd!amos.ucsd.edu!hartung BITNET - hartung%amos.ucsd.edu@sds.sdsc.edu
person@plains.UUCP (Brett G. Person) (03/04/90)
MO NO NO! Keep the moderator. A lot of *bad* things could happen if we don't have someone monitor the programs we get. Does anyone remember the famous Mean 18 incident? I thought so. -- Brett G. Person North Dakota State University uunet!plains!person | person@plains.bitnet | person@plains.nodak.edu
ash@mlacus.oz (Ash Nallawalla) (03/04/90)
> postings in the last week. Where were YOU, Richard?
I too don't know where I was, but I am sure that some postings must have
skipped my site. I know that comp.virus was inactive _here_ for most of
February, and cbipcd was pretty sparse. (I am in Australia) Anyway, welcome
to the new moderator, whoever he or she may be.
--
=============================================================================
Ash Nallawalla Tel: +61 3 823-1959 Fax: +61 3 820-1434
ZL4LM/VK3CIT Postal: P.O. Box 539, Werribee VIC 3030, Australia.