From LOJBAN%CUVMB.bitnet@YaleVM.YCC.YALE.EDU Sat Mar 6 22:54:44 2010 Received: from YALEVM.YCC.YALE.EDU by MINERVA.CIS.YALE.EDU via SMTP; Thu, 11 Mar 1993 03:12:06 -0500 Received: from CUVMB.CC.COLUMBIA.EDU by YaleVM.YCC.Yale.Edu (IBM VM SMTP V2R2) with BSMTP id 0143; Thu, 11 Mar 93 03:11:03 EST Received: from CUVMB.BITNET by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with BSMTP id 4212; Thu, 11 Mar 93 03:11:57 EST Date: Thu, 11 Mar 1993 03:09:15 -0500 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: Re: ADMIN: Lojban Announcements List X-To: nsn@MULLIAN.EE.MU.OZ.AU X-Cc: lojban@cuvmb.cc.columbia.edu To: Erik Rauch Status: OR X-From-Space-Date: Wed Mar 10 22:09:15 1993 X-From-Space-Address: @YaleVM.YCC.YALE.EDU:LOJBAN@CUVMB.BITNET Message-ID: The main reason we haven't implemented this is that announcements worth posting seem to be few and far between, and 1) I have no more complete a set of net addresses than the current Lojban List subscriber set and 2) my observations are that net addresses tend to have a halflife in months. Thus, if we did manage to gather 200 names on the list, and sent out one message per month, we would get a dozen or so bounce messages each time, and be dropping those people from the list (as well as filling up our mailbox). With that frequency rate, the lurkers of the world will not remember or bother to keep the list updated with their current address. The net result in my opinion is that within a year, the list would have degraded to the point that it is virtually identical to Lojban List, with maybe a dozen other people that are interested in Lojban but don;t have time to read the occassional high volume of Lojban List traffic. We would probably also lose half of the Lojban List membership to this announcements list, which might or might not be a big loss. That is why I personally haven't done anything about this. lojbab