Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Moderator Tools And Techniques  <--  <--- Return to Home Page
   Networked Database  Moderator Tools And Techniques   [12 / 22] RSS
 From   To   Subject   Date/Time 
Message   Moderator    All   ECHOMODS Echo Rules   September 1, 2017
 12:00 AM *  

 Conference rules for the ECHOMODS echo:                  rev. 25 Feb 13
 Posting Frequency: 1st of the month.
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 Rules and info
 Your host and moderator:  mark lewis, 1:3634/12
 Last updated February 25, 2013 (formatting and moderator changes)

 What it's for:  A place for moderators to exchange tips, tricks, and
 information regarding moderation of Fidonet echoes and other forums.

 Any and all discussion regarding the management and moderation of a
 Fidonet conference is welcome.

 Users and point operators must request permission to post in this
 echomail conference, either via routed netmail, or via the sysop
 hosting the user or point system.

 Permission will be granted to recognized moderators of Fidonet echomail
 conferences who are not themselves the operator of a system listed in
 the Fidonet nodelist.

 The conference may be made available as read only to all other points
 and users.

 Moderators who are not Fidonet system operators may send email to
 mark.lewis@ftn.wpusa.dynip.com with a subject line indicating that the
 message is requesting write privileges in this conference. Parties
 requesting access via email must state which listed Fidonet system they
 will be using to post in the conference, or a point address derived
 from a listed Fidonet system. When permission to post is approved it
 will be posted in the echo, and routed netmail sent to the sysop
 hosting the requester. IF an individual requesting posting privileges
 is not known to the moderator his/her request will be conveyed to the
 echo for the purpose of seeking additional information from echo
 participants.

 The usual rules of Fidonet echomail apply. These include the use of
 real names, proper displaying of address and other information on
 messages originating from your system, etc.

 Gateways to/from other networks must be approved by users of the
 conference. IF approved any gateway must work in both directions. The
 operator of any approved gate is responsible for all traffic entering
 the echo through that gateway.

 Moderation issues will be handled by Fidonet netmail only.

 Other than that, come on in, pull up a chair!  Thanks for participating
 in the Fidonet echomods conference.

 Richard Webb : moderator emeritus
 Mark Lewis   : moderator


 * Origin: (1:3634/12)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Moderator Tools And Techniques  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0847 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_sk5to8e9bfkot8le6aj9pr3d82, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_sk5to8e9bfkot8le6aj9pr3d82, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_sk5to8e9bfkot8le6aj9pr3d82, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0