-=> On 06-29-04  09:37,  Thom Lacosta <=-
 -=> spoke to Dale Shipp about test! <=-

 TL> I think that anyone who gates a fidonet echo needs to ascertain
 TL> whether or  not the moderator of the echo(es) in question allow gating.

   I definitely agree.

 TL> I'm not convinced that any of the echoes I moderate should
 TL> be gated if there are not neasures taken to prevent 
 TL> unlimited posting to them by folks over which the gateway 
 TL> operator has no control.

   The last phrase in what you say above is the key issue.  If the BBS
   Sysop distributes the messages and allows posting by those over who
   he/she has no control, then it could quickly become a bad scene.
   This is certainly one of the prime reasons why many moderators are
   against gating of their echos -- it is my primary reason.

 TL> There is a field in the echolist description that allows moderators to
 TL> indicate whether or not they allow their echoes to be 
 TL> gated...and I suggest that moderators with concerns make 
 TL> use of that field.  That type of usage would allow a
 TL> gateway operator to quickly ascertain whether or not they 
 TL> have permission to gate the echo.

  I just looked at my submission and notice that I have GATE NO.  The
  restriction against gating of the echo I help moderate is also in the
  rules file which is distributed each month.  Guess that covers me:-}}

  There is one additional point though.  Not everyone agrees as to what
  constitutes "gating".

  In my view, it is distributing an echo to another system via non
  fidonet distribution methods and/or receiving input for the echo in a
  similar manner from other systems.  I am strongly against such
  actions in either direction.

  In my view, making the BBS message data base available for users in a
  variety of formats (Web page, NNTP, QWK packets, etc.) is *NOT*
  gating.  I am not against such actions, so long as the potential
  format differences are handled in a reasonable manner.


                        dale (at) min (dot) net
                              (1:261/1466)


... Shipwrecked on Hesperus in Columbia, Maryland. 23:31:38, 29 Jun 2004
___ Blue Wave/DOS v2.30

--- Maximus/NT 3.01