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 Point usage discussion and syste...  <--  <--- Return to Home Page
   Networked Database  Point usage discussion and syste...   [198 / 890] RSS
 From   To   Subject   Date/Time 
Message   Marc Lewis    All   AUTOMATIC RULES POSTING P   March 25, 2019
 12:04 AM *  

========================================================================
POINTS ECHO RULES AND POLICIES
Revised Nov 30, 2018
English is the official echo language.
========================================================================
ALL USERS WHO HAVE ACCESS TO THIS ECHO MUST READ THIS. BY POSTING
MESSAGES IN THE ECHO, YOU AGREE TO ACCEPT AND ABIDE BY THE RULES OF THIS
CONFERENCE AS HERE POSTED.

This conference may be made available to responsible users, point nodes,
and full nodes (Boss nodes/SysOps).  If traffic gets too heavy, it may
at some future date be restricted to points and full nodes only.  This
is the POINTS echomail conference.  This, along with many other echomail
conferences is distributed worldwide. Please keep this in mind when
entering messages. Keep your messages brief and to the point, and do not
be excessive in QUOTING the contents of other messages.

Description/Topicality...
All messages posted here must consist SOLELY of helpful & informative
material regarding POINTS and BOSSNODES.  HELP for all topics concerning
POINT operation, is appropriate here including the support for specific
Point related software by their Authors. This is not a my point setup
and/or product is better than your point setup and/or product echo.  Be
constructive and polite.  Having said that, this echo has been a very
professionally handled echo, and is generally frequented by a very
respectable group.  FidoNet is a police state so we must post rules, but
the flavor of this echo is simply to be informative and have fun.
Message handling and restrictions...

1.  Messages must remain on the topic of this conference as described
above and in the current EchoList.   Discussion of other topics is
grounds for the offending person or node to be banned from this
conference.
2.  Foul or obscene language, personal invectives, and "widget wars" will
not be tolerated.
3.  Encrypted, encoded or rotated messages are forbidden.
4.  Keep the quoted portions of your messages SHORT.  Excessive quoting
adds to expense and overhead.  Quote just enough to identify the
thread of the conversation for other users.  Use enough of the
original material to be sure the thread IS identified.
5.  Reasonable announcements for NEW or REVISED Point or related software
by Authors is ok, as long as it does not become too frequent.
6.  The use of "Visible ASCII Control Characters" ie: ASCII 31 and
below or "High ASCII Characters" ie: ASCII 129 and above is
prohibited in this echo except for language characters that are part of
someone's name, etc.
7.  Messages must originate with a real name, no alias names please.
8.  Gating this Echo to the internet is forbidden without Moderator
permission.  Garbage mail coming back into the Echo from the internet
via your gate will result in a prompt and permanent severing of your
link.
Moderator Policy/Continuity...
1.  All rules violations are to be addressed ONLY by the Moderator, or
Co-Moderator.
2.  Questioning or discussion of Moderator policy in the open echo is
off topic, except that the Moderator reserves the right to post
special messages relating to such policy and rules from time to
time for the edification of all participants.  The Moderator will
listen to and consider, any suggestion or criticism sent by
private hub or host-routed NetMail.  If there is a subject re
Moderator policy that needs to be discussed it will be brought to
the echo by the Moderator.
3.  The Moderator shall have the right:
a. To appoint Co-Moderator(s) or Alternate Moderator(s)
b. To set the rules for selection of his/her replacement at any
time.
c. The right to revise these rules at any time.
4.  In the event of the incapacity or unwillingness of the Moderator to
continue to serve, then the Co-Moderator shall have all the rights
ascribed to the moderator.
In compliance with FidoNet Echo Policy, the conference rules will be
posted no less than once per month, and nothing in these rules will
supersede or replace any valid FidoNet rule or policy.
========================================================================
FidoNet International POINTS echomail conference
Marc Lewis @ 1:396/45, Moderator
========================================================================
Recompiled 30NOV2018 @1512

--- MPost/386 v1.21
 * Origin: Sursum Corda! BBS=Huntsville,AL=bbs.sursum-corda.com (1:396/45)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Point usage discussion and syste...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0851 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_m3aquu3m4opd98ap93nd9vgib6, 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_m3aquu3m4opd98ap93nd9vgib6, 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_m3aquu3m4opd98ap93nd9vgib6, 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