ͻ
                                                                        
  N   I   R   V   A   N   A   N   E   T   (tm)    C  H  A  R  T  E  R   
                                                                        
ͼ

01  What NIRVANAnet(tm) Is

    NIRVANAnet(tm) consists of a group of Open Access BBSes, which
    carry a number of identical message echoes and file echoes. All
    boards will carry a minimum of two thirds of the message echoes
    offered by the net, as well as NNSYSOP and Netmail. In addition to
    NIRVANAnet(tm) Message Areas, NIRVANAnet(tm) members can also carry
    NIRVANAnet(tm) Text File Echoes, NIRVANAnet(tm) Public Key
    (encryption) Distribution Echoes, and other NIRVANAnet(tm) data
    feeds to be announced.

02  Why This Charter Exists

    This Charter is written not to be excessively bureaucratic, but
    simply because, in order for a network like this to exist and grow,
    it needs to have some sort of basic structure. This Charter
    attempts to nail down that basic structure so that NIRVANAnet(tm)
    will last for decades.

03  Hubs

    A Hub is defined as any BBS System that is feeding the
    NIRVANAnet(tm) message echoes to two or more NIRVANAnet(tm) BBSes.

04  Net / Local Net

    A Net or Local Net is all of the Nodes that get data from one Main
    Hub.

05  Node

    A node is a single BBS system.

06  Hub Duties and Responsibilities

    Hubs have to connect with each other at least twice a night in order
    to transfer all echomail, netmail, and file echoes. The sysops
    running these systems must be very technically proficient and have
    systems which are reliable. They must coordinate mail transfer
    periods with the other hubs and nodes that they feed data to.

    A Hub is responsible for routing mail around systems that go down
    within their Local Net.

    Hubs work with new Nodes to iron out technical problems and to
    get the new Nodes on-line.

    Hubs will pass nodelist updates on to the Nodes they are feeding.

    Hubs also have all of the duties and responsibilities of Nodes.

07  Node Duties and Responsibilities

    Nodes will do their best to remain Open Systems and resist the urge
    to control their users. Nodes must call their Hub at least once a
    night, but preferrably twice, to pick up mail. Nodes will make
    NIRVANAnet(tm) Info Packs available to all callers, so that others
    can join the net.

08  Voting

    Voting is used for electing network officers, amending the
    NIRVANAnet(tm) Charter, and when adding or ejecting nodes.

    Votes can be for, against, or abstain. An abstain vote does NOT
    count as a vote. If a person does not vote, this is counted as an
    "abstain" vote. (This means that in a simple majority vote, if there
    there are 100 nodes in the net, and 49 vote "YES" and 48 vote "NO",
    then there are 3 abstensions, the YES votes win.)

    Voting is done by placing the question on the NNSYSOP board and
    asking for a vote. Once a question has been put to a vote, all
    voting members must vote within 14 days, unless stated otherwise
    within the Charter. There is no such thing as a "secret ballot".

    If a new node is added while a vote is in the middle of being
    conducted, the new node does not get a vote.

    The NNC tallies all votes and posts a running total of who voted
    "Yes" and who voted "No" up until the voting period is over. At
    which time the NNC will post the final results.

    A Voting Member may change their vote at any time up until the
    voting period is over.

    All votes to elect Net Officers are by simple majority of the
    votes cast.

    Amending the Charter takes a 2/3 majority of ALL voting members.

    See the section on "New Systems" for information on voting in
    new systems.

    See the section on "System Expulsion" for information on voting
    when cutting a system's data feed.

    All other votes are by simple majority, unless otherwise stated in
    the Charter.

09  Who Votes

    In order to vote, a member must have an active system. There is one
    vote per BBS system, and no one gets more than one vote.

    Generally, if a person's name appears in the nodelist, then they're
    eligible to vote, which is why the NNC also conducts elections.

10  Net Officers

    There are six elected positions for Net Officers in
    NIRVANAnet(tm): International Network Coordinator (INC), Network
    Nodelist Coordinator (NNC), Network Data Router (NDR), Network
    Technology Advocate (NTA), Network Outreach Coordinator (NOC),
    and Network Public Relations (NPR).

    All votes to elect Net Officers are by simple majority of the
    votes cast. Each officer is elected for a period of two years.
    No one may have more than one official position.

    An officer may step down before their two years are up if they
    feel they can no longer carry on with their duties. An officer
    must step down if they no longer qualify as a voting member.

    Each officer has an Official Title as reflected in the Charter
    and a Silly Public Title to reflect the whimsical nature of the
    net. Each candidate gets to pick their own Silly Public Title
    which they will use for the duration of their term of office.
    Furthermore, they must state what Silly Public Title they will
    use when they declare their candidacy.

    Once an officer's term is up an election is called. Once an
    election is called voting members have 10 days to declare their
    candidacy. After the 10 days are up, voting begins. Voting
    continues for a period of 14 days. During the two weeks the NNC
    will tally and post the results, posting the final results at
    the end of the two week voting period. If the election is for
    the position of NNC, the INC will tally and post the votes.

11  International Network Coordinator (INC) Responsibilities

    The INC is ultimately responsible for everything, but spends most
    of their time coordinating the efforts of the other officers,
    resolving disputes, and filling in where necessary.

12  Network Nodelist Coordinator (NNC) Responsibilities

    Maintains the NIRVANAnet(tm) nodelist. Adds new nodes to the
    nodelist and deletes boards which are no longer active. Changes
    board information as necessary. Sends out nodelist updates to all
    Main Hubs.

    The NNC conducts all elections and tracks votes. Each
    officer's last date in office is stated in the nodelist.

    The NNC also puts together the NIRVANAnet(tm) Info Packs which
    should be available on every node. These packs contain the
    NIRVANAnet(tm) Charter, an application, the NIRVANAnet(tm)
    Nodelist, and anything else the NNC deems appropriate.

13  Network Data Router (NDR) Responsibilities

    Makes sure that echomail, netmail, and file echoes are flowing
    smoothly. Works with the hubs to make sure that mail is not
    being lost. Has the final say in determining the routing for
    mail between the various Hubs. Is responsible for adding new
    echomail areas to the backbone as requested by nodes. Is
    responsible for scheduling mail run times so that echomail will
    flow quickly.

    Makes sure that those boards that wish to participate in the
    file echoes are getting their files. Makes sure that boards
    which do NOT wish to participate in the file echoes do not get
    stuck with the cost of transporting files. Figures out routing
    for files. Adds new file echoes as needed or requested.

14  Network Technology Advocate (NTA) Responsibilities

    Researches new networking technologies and software. Finds ways
    to make communication private, faster, and cheaper. Suggests
    ways that NIRVANAnet(tm) members can implement encryption,
    remailers, Internet technologies, and other cutting edge
    technologies that can be adapted for BBS users. Reports findings
    on a regular basis to other NIRVANAnet(tm) members.

15  Network Outreach Coordinator (NOC) Responsibilities

    Looks for BBS systems that would qualify for NIRVANAnet(tm).
    Tries to open up new cities and new regions to NIRVANAnet(tm).
    Spreads the NIRVANAnet(tm) gospel to other sysops and users.

16  Network Public Relations (NPR) Responsibilities

    Tries to get NIRVANAnet(tm) in the news. Sends info to any
    publication or broadcasting service that will publicize
    NIRVANAnet(tm). Makes sure that NIRVANAnet(tm) BBS Systems are
    included in any and all BBS Lists. All publicity is good
    publicity.

17  Users

    Do not count.

18  Minimum Technical Standards

    There are minimum BBS standards involved in NIRVANAnet(tm). The
    proposed system would need to have a minimum of down time, menus
    should have a planned appearance. Menu options should actually do
    something (what they do is up to the sysop), and systems should be
    able to generate packets and receive them on a regular basis.

19  New Systems

    In order to become a node in the network a sysop must first fill
    out a NIRVANAnet(tm) Application Form, electronically sign it, and
    upload it to a NIRVANAnet(tm) BBS.

    The sysop of the NIRVANAnet(tm) BBS will call the applicant's BBS
    to make sure that it is an OPEN ACCESS system, as defined by the
    NIRVANAnet(tm) Charter.

    If the NIRVANAnet(tm) BBS decides that the BBS qualifies according
    to the Charter, the sysop will post the application on the NNSYSOP
    echo. After 10 days, if there are no votes against admitting the new
    system, then the INC and NNC will do what needs to be done to get
    the new system connected.

    If any voting member votes against admitting the new system, the
    system is NOT admitted to NIRVANAnet(tm). They may try applying
    again after three months have passed, if they wish. (This is why
    it's a good idea for applicants to make SURE that their system
    will pass muster before applying to the net.)

    After being admitted, any new system must be hooked into the net
    within two weeks. It is assumed that before a system is admitted,
    it is capable of exchanging echomail packets already. The two week
    margin allows for any technical problems which might crop up.

20  Open Access

    In a perfect world, Open Access means no registration, no
    validation, no complex new user questionnaires, no requirement for
    users to enter real names, addresses, phone numbers, birthdays,
    gender, or other personal information, handles are allowed and
    encouraged, users are trusted, freedom of speech reigns supreme,
    knowledge is available to everyone, and no discrimination based on
    age, sex, race, religion, drug use, or mental stability. It also
    means that once a person is on-line they can immediately read and
    write messages, download files, play games, and use any other
    functions that the BBS provides.

    For the purposes of NIRVANAnet(tm), Open Access means that we
    require:

      * No requirement for users to enter real names,
        addresses, phone numbers, birthdays, gender, or
        other personal information.
      * No "validation" of new users.
      * No complex new user questionnaires.
      * Handles are allowed and encouraged.
      * No discrimination based on age, sex, race, religion,
        drug use, or mental stability.
      * Once a person is on-line they can immediately read
        and write E-Mail, local messages, NIRVANAnet(tm)
        Netmail, and NIRVANAnet(tm) Echomail.
      * Once a person is on-line they can immediately
        download files that the BBS obtained from the
        NIRVANAnet(tm) Text File Archives or through the
        NIRVANAnet(tm) Text File Distribution System.

    We encourage sysops to keep their BBSes to be as open as possible,
    and to allow full access to all functions and areas within the BBS
    to all callers.

21  New User Questionnaires

    If your BBS software will not allow you to turn off these nosy new
    user questions, you can use a hex editor to change them to
    something less noxious. (Such as changing "Enter Your REAL Address"
    to "Favorite Color".) Better yet, switch your software to something
    less Big Brotherish and tell the author of the software why you're
    switching. If you cannot turn off these questions and are unable or
    unwilling to use a hex editor you will not be admitted to
    NIRVANAnet(tm).

22  Files

    Sysops are encouraged to be as generous with file ratios as
    possible, or to give files away with no ratios.

23  Exceptions

    Unfortunately, we do not live in a perfect world. Many countries
    and states place restrictions upon free speech and free expression.
    Sysops who violate these restrictions can end up fined, imprisoned,
    or worse. Because of this governmental interference, sysops may be
    required by law to restrict information about sex to people over
    the age of 18 or 21, or in some areas, the information may not be
    provided at all. Some countries do not allow people to exchange
    information about explosives or weapons, in some jurisdictions you
    cannot discuss entry codes for getting into computer networks, and
    passing out credit card numbers is verboten just about everywhere.

    Since we don't want Sysops to end up in jail, it is permissable to
    restrict access to some areas IN ORDER TO COMPLY WITH GOVERNMENT
    REGULATIONS. However, restrictions should be at the absolute
    minimum levels needed to be acceptable to the local authorities.
    For instance, if it is legal in your area to give access to erotic
    material by having users sign a document that says "I am over 18",
    then by no means should you be requiring them to send in
    photocopies of their driver's licenses.

    If your government says that some information may not be provided
    at all or you will go to jail, we advise you to delete such
    information from your system.

24  NNSYSOP

    Every system is required to carry NNSYSOP, the PRIVATE
    NIRVANAnet(tm) Sysops-only conference. It should be read by the
    BBS' sysop(s) at least once every three days, unless there is a
    really good excuse not to (e.g. Hardware downtime, vacation,
    spousal violence, etc). ALL posts should be read, not just
    addressed posts. Members of the immediate household are also
    allowed to read NNSYSOP.

    Sysops are the users or user with the most access on the BBS. If
    there are multiple EQUAL sysops, they may all read and partcipate
    in NNSYSOP. If there are multiple sysops with UNEQUAL access, only
    the sysop(s) with the most access (the primary sysops) may read
    or participate in NNSYSOP.

    A vote must be taken to allow anyone else to read (or participate)
    in NNSYSOP. Allowing anyone other than the primary sysop(s) or another
    member of the household to read the NNSYSOP echo without permission
    of the voting members may result in cutting the network feed of the
    offending system.

25  New Topics

    The NDR must add a new topic if four or more NIRVANAnet(tm) boards
    request that it be added. The sub will be available to all other
    member systems. Requests can be made on the NNSYSOP echo.

    If fewer than four boards request a new topic, it may be added or
    the boards requesting the topic may be asked to network the
    messages directly among themselves, at the discretion of the NDR.

26  Echoes

    All NIRVANAnet(tm) echos will be made available to all
    NIRVANAnet(tm) BBS systems. If an echo is getting too congested, it
    may be split into two or more smaller echos. All NIRVANAnet(tm)
    echos have echo names beginning with "NN" to make things easier on
    sysops who carry multiple networks. A sysop may choose anything
    they like as the local name for an echo, but the echo name should
    reflect the original intent and purpose of the echo.

    NIRVANAnet(tm) echos may NOT be made available to any BBS system
    that is not a member of NIRVANAnet(tm). If a NIRVANAnet(tm) BBS is
    caught sending a feed to a non-NIRVANAnet(tm) BBS, the offending BBS's 
    feed will be cut.

27  Echomail Moderators

    Any NIRVANAnet(tm) sysop may nominate any NIRVANAnet(tm) user to be
    an Echomail Moderator by posting a their nomination on the NNSYSOP
    echo. If no voting members object within 10 days, the nominee
    becomes the new moderator. If any voting member objects to the
    nomination, the moderator of the echo remains the same as it was.

28  Regional Echoes

    If an echo is of regional interest only, such as "Places to Go in
    the Bay Area", it will begin with "NN" plus the Local Net number
    plus the name of the echo. Example: NN900PLACES. These echoes will
    still be available to ALL NIRVANAnet(tm) BBS systems.

29  Netmail

    All NIRVANAnet(tm) systems will make netmail available to their
    users if it is technically possible to do so. This allows users to
    send private mail to other users on other NIRVANAnet(tm) systems.

30  Encrypted Messages

    All NIRVANAnet(tm) systems agree to allow users to send encrypted
    messages to one another using E-Mail, Netmail, and Echomail. Users
    will be encouraged to use E-Mail and Netmail whenever possible.

31  Free Speech

    NIRVANAnet(tm) is a free-speech network. Posts will not be deleted,
    unless they contain:

      * Credit card numbers
      * Phone company calling card numbers
      * Names and passwords for private systems
      * Unsolicited personal phone numbers

    Sysops should try to keep messages on-topic. Messages can be moved
    from one area to another and users can be yelled at, but posts
    should not be deleted for being off-topic. The same restrictions
    apply to flames, which reduce the amount of communication that's
    occurring. Often, it is a good idea to forward flames to the flame
    echo, that's what it's there for. It's also why we keep the number
    of posts on that sub VERY low. Sysops should also attempt to keep
    personal messages and 1-to-1 communiques off the netted subs, and
    keep them in e-mail, netmail, or in a local message base. Finally,
    when quoting a message, users are expected to quote only the
    relevant part of the message, not the entire thing, tag lines and
    all. This is to help reduce the amount of traffic crossing the
    network and to keep costs down.

32  Multiple Networks

    If a BBS system carries multiple networks, we hope that the sysop
    will make NIRVANAnet(tm) the "primary" or "featured" network of
    their system. Sysops who want to add NIRVANAnet(tm) just because
    they are "collecting networks" for their system will be discouraged
    from joining NIRVANAnet(tm).

33  Multiple Network Conflicts

    If your BBS system is a member of another network that does require
    real names, we encourage you to tell them to shove that requirement
    up their collective asshole.

    If that doesn't work, see if you can set up your system to allow
    users to enter a "real-sounding" name that is used whenever they
    access this other network.

    If that still doesn't work, you must decide which network you want
    to keep on your system, NIRVANAnet(tm) or "BigBrotherNet."

34  Off-Topic Messages

    If an echo gets way off-topic, it may be necessary for several
    sysops to coordinate moving messages and chastising the offending
    users. These actions can be coordinated by using the NNSYSOP board
    or netmail.

35  Off-Topic Users

    Some users have one axe to grind and they grind it on every single
    message base they come to. Usually this malise of being unable to
    recognize topics comes in one of three forms: Political, Religious,
    or Incoherent Abuse and Flaming. If you have a user on your system
    with this problem, try to reason with them and get them to stay on
    topic. In extreme cases, it may be necessary to restrict them to
    posting on one message echo. Sysops are expected to use their own
    best judgement for this, and to try every available means necesary
    before restricting users.

36  Spelling

    All NIRVANAnet(tm) sysops must be able to spell "NIRVANAnet(tm)"
    correctly.

37  Language

    The official language of NIRVANAnet(tm) is English, unless someone
    can think of a better language.

38  System Expulsion

    If a NIRVANAnet(tm) BBS is not an open system, or violates the
    letter or the spirit of the NIRVANAnet(tm) Charter, they may be
    expelled from the net.

    If a sysop thinks that a system should be expelled from
    NIRVANAnet(tm), they must first post their reasons for expulsion
    in the NNSYSOP echo in order to give the offending system a
    chance to respond. If the problem is not resolved to the offended
    sysop's satisfaction, the offended sysop can call for a vote.

    First there is a vote to give the system a warning. If at least 4
    voting members are in favor a warning then a warning is given to
    the offending system to clean up its act, along with a date by which
    the system must be acceptable. This date must be a minimum of two
    weeks from the warning date. The warning must state exactly what is
    unsatisfactory about the system.

    When the expulsion date has been reached, a vote will be taken to
    expel by the voting members. If 2/3 of the votes cast are votes
    to expell, the system will be kicked out of NIRVANAnet(tm). The
    system being expelled does not get a vote.

39  Charter

    Changes can be made in this charter with approval of 2/3 of the
    ALL of the Voting Members of NIRVANAnet(tm).



    This Amended Charter was adopted on March 31, 1997 by:

                Taipan Enigma   & the Temple of the Screaming Electron
           Poindexter Fortran   realitycheck
                   Mick Freen   Lies Unlimited
                       Szarka   Sea of Noise
                        Liana   The Stage
        Tiny Little Super Guy   The Ether Room
                El Observador   El Observador
               G.A. Ellsworth   Cool Beans!
                Cyber Trollis   DUSK Til Dawn
                        Razer   People's Republic of Dark Cartel
                       Luthor   Strange Days
