The Arcade BBS

home *** CD-ROM | disk | FTP | other *** search

/ The Arcade BBS / arcadebbs.zip / arcadebbs / WWIVUTIL / NET34.ZIP / WWIVNETP.DOC < prev

Wrap

Text File | 1994-08-06 | 52.3 KB | 1,103 lines

WWIVnet Policy Document Revised 8/6/94 1. ORGANIZATION WWIVnet originally began in 1988 with 25 charter members who helped Wayne Bell develop the network software and debug it. Since that time it has spread from a small Los Angeles-based system of local boards to an international network. Currently, the network software is in its 32nd version although there will undoubtedly be many future versions written as well. These versions are referred to as Net1, Net2,...Net20, etc. The international network has Wayne Bell as its head. The network is organized into groups with each group having a Group Coordinator. Currently there are 14 groups. Each group is composed of approximately 100 systems which may be located in one or more area codes. Each area code where there are more than 5 network systems has its own Area Coordinator. This organization is reflected roughly in the organizational chart below: ┌────────┐ │ NC │ └───┬────┘ │ ┌─────────────────┴┬──────────────┐ │ │ │ ┌─────┴─────┐ ┌───────┴────┐ ┌──────┴──────┐ │ │ │ │ │ │ │ GC 1 │ │ GC 2 │ │ GC 3-14 │ └───────────┘ └─────┬──────┘ └─────────────┘ │ │ ┌────────────────┼───────────────┐ │ │ │ ┌──────┴─────┐ ┌──────┴────┐ ┌──────┴─────┐ │ AC │ │ AC │ │ AC │ │ │ │ │ │ │ └────────────┘ └─────┬─────┘ └────────────┘ │ │ ┌─────────┬─────────┴───┬──────────┐ │ │ │ │ ┌──┴───┐ ┌──┴────┐ ┌────┴───┐ ┌───┴────┐ │Node │ │ Node │ │ Node │ │ Node │ └──────┘ └───────┘ └────────┘ └────────┘ General organizational chart for WWIVnet depicting the Net Coordinator at the top with authority overall in terms of policies, procedures, rules, etc. Serving the NC are the GCs. The GCs report to the NC and receive information from the ACs. The ACs receive information from the individual nodes in the area code and report to the GCs. For those areas that have fewer than 5 systems, the Group Coordinator functions as the area coordinator for the small area code. An understanding of the roles of the Group Coordinator and Area Coordinator facilitates cooperation and prevents arguments and disputes. The rules, regulations and suggestions which are presented here are designed to insure that the network functions well and that friction between the components of WWIVnet does not develop. However, these rules should not be forced to apply to situations where they do not seem to logically fit. Instead, the rules can be adapted to the situation. These rules should not be regarded as "carved in stone," for WWIVnet is dynamic and undergoing evolutionary changes as it grows. These documents will be revised from time to time to reflect these changes. 2. Group Coordinator The group coordinator is a position developed by Wayne in response to growth in the network and suggestions of many interested parties. The network growth necessitated a division of duties so that the updating of the network could occur in smaller packages; that is, there was up through NET19 a natural limit of 32k to the length of BBSLIST.NET. As the number of systems grew and the length of the file approached its natural limit, Wayne was faced with the decision of either developing a new organizational structure or telling network members that no new systems could be added. For obvious reasons, the first alternative was selected. In addition to serving as the Area Coordinator for area codes where there are five or fewer systems, the Group Coordinator has the following duties: 2.1 BBSLIST Receive from ACs and forward to Wayne Bell updates to the BBSLIST.x (i.e., information on systems being added to the network, changes in phone numbers, modem type, etc). In addition, the GC is responsible for maintaining the registration numbers in the BBSLIST of those boards that have registered either the WWIV BBS software or the network software. More information on these types of registration is found in the appendix to this policy document. 2.2 CONNECT Receive from ACs additions, deletions, or other changes to the CONNECT.x list for the GROUP as well as changes which are to be made to the CONNECT.0 file which reports inter-group connections. The GC for either side of the connection may report the new connection to the NC except in the case of connections to net servers. A net server is a board with a node number between 1010 and 1999 which does not have normal users and which functions solely to facilitate the transfer of network mail. Connections to these nodes must be approved and transmitted to the NC by the GC for that server. On the other hand, the deletion of a connection to a server may be handled by either the server's GC or the GC for the node connecting to the server. 2.3 Routing The GC should help determine the best routing for messages. This function usually involves helping boards within a particular state to find out-of-state (and therefore cheaper) long distance connections. The GC does not have the power to force a particular out-of-state connection. The routing function of the GC is purely advisory. 2.4 Prevent Isolation The GC helps to insure that no system or group of systems becomes isolated (i.e., without a connection to the outside world). 2.5 Arbitrate Grievances The GC serves as first step in grievances between sysops and their Area Coordinators and in other area disputes. If the GC is unable to successfully arbitrate the contention, he may ask that Wayne Bell create a Problem Resolution Committee (PRC) to attempt to solve the difficulty. These difficulties are those which arise among sysops, which threaten to destroy the enjoyment of the network, and which are not related to policy and procedure. Policy and procedure matters are handled by the GCs and the NC as a body. The Problem Resolution Committee is currently in the experimental stages and may be done away with if it fails to prove to be an efficient way of dealing with such problems. The final step in problem resolution is to have Wayne Bell resolve the problem. 2.6 Election (appointment) of ACs The GC may appoint an AC for an area code or he may have one elected. If the AC is elected, then the GC facilitates the election process when Area Codes hold AC elections. Such facilitation may involve the GC's conducting the election, counting the votes, announcing the winner, etc. 2.7 Insure Compliance with the 60-day trial period The GC checks WWIV and WWIVnet registrations to insure that new nodes have complied with the 60-day trial period requirements. The GC will normally encourage the node to comply with the registration requirements and may drop it from the network listing if it fails to comply or indicates that it has no intention of compliance. 2.8 Recommend Removal of a Node A board may be removed from WWIVnet for many different reasons. These reasons include such things as (a) inability to make connections, (b) failure to register the software, (c) participation in illegal activities involving the network, (c) unauthorized distribution of WWIV source code, (d) repeated offensive and obnoxious behavior which prevents others from enjoying the network, etc. This list of reasons is NOT all inclusive but is representative of the types of things which might cause a node to be removed or recommended for removal. In situations like reasons (a) and (b) removal from the network is not permanent and is not "for cause." That is, the board is removed in case (a) because it cannot make its connections for whatever technical reasons and would be readmitted as soon as it had solved its technical difficulties. Removal for reason (b), non-registration, would permit the board to be reinstated after it had registered. On the other hand, removal for "cause", such as implied by reasons (c) and (d) would involve the joint decision of all GCs and the NC. More specific procedures to be followed in a case of removal "for cause" are found in the appendices to this document. 3.0 Area Coordinator The duties of an Area Coordinator (AC) are simple and few; however, these activities are extremely important for the proper functioning of WWIVnet. The duties are as follows: 3.1 Admission of new Boards Investigate net applicants and either assign them a node number or provide them with a reason why no node number is being assigned. This function is discussed more thoroughly under rules and regulations below. Any time that a board is refused admission to WWIVnet, the AC should send a copy of the refusal to the GC as well as to the applicant. 3.2 Forward information to Group Coordinator Information regarding the addition and deletion of boards from the network as well as information regarding changes to the information in the BBSLIST and CONNECT files for boards in the area code is sent to the GC. 3.3 Area Code Policy regarding Part Time Boards The area coordinator no longer has the authority to state the area code's policy regarding the admission of part-time boards (not up 24 hours a day) to the network. National WWIVnet policy regarding the participation of part-time boards is stated in the appendices. 3.4 Serve as Arbitrator Between Sysops in Arguments The AC may function as an arbitrator of disputes between sysops in the area code; on the other hand, he may refer such disputes to the GC if he wishes. 3.5 Prohibited Actions An AC may not do any of the following: (a) charge anyone a fee to allow them to be admitted to WWIVnet, (b) require any board to have a connection against its wishes, (c) refuse admission to the network to a board based on the race, color, creed, age, or national origin of the sysop, (d) refuse admission to a board because of the type of software that it runs if that board is WWIVnet compatible. Any question of admission based on the software being run should be referred to the GC or NC of the network. An AC may not require a board to be running longer than 1 week before admitting them to the network. An AC does not have the authority to remove any one from the network "for cause." (See appendix on removal from the network). The AC may recommend that someone be considered for removal, or may ask that a board be removed because it is unable to make its net connections. 3.6 Permissive Actions -- Not an AC function There are other things that an AC may wish to do but they are NOT part of the AC's function. For example, the AC might establish an Area Code Sysop's Forum, help boards to get setup, provide other technical assistance to new boards, etc. The AC may also serve as the long distance hub for the area. None of these things are required of an AC nor are such activities limited to an AC. An AC should attempt to make it quite clear to the members of the area code when he is "wearing his AC hat" and when he is not. 4. RULES AND REGULATIONS WWIVnet is characterized by very few rules and regulations. Those that do exist are either absolutely necessary to the proper functioning of the network or are common courtesies that should be extended between cooperating systems. I will use rule and regulation interchangeably in the discussion which follows. There is no difference between the terms as used here. I have done my best to organize these rules in terms of whom they apply to. Since every AC or GC is also a Sysop, the rules for Sysops apply equally to the ACs and GCS. 4.1. Requirements for GC The person serving as GC was either (a) nominated by Wayne Bell or someone else such as an AC or (b) self nominated due to the connections maintained. The individual has been accepted by Wayne, by the AC's with whom he/she must relate, and possibly by a vote of the sysops in the area as well. However, the process of becoming a GC is NOT necessarily a democratic one. That is, being a Group Coordinator is not the result of a popularity contest; instead, it is the result of demonstrated maturity in the network, willingness to serve, and having the confidence of the ACs and Wayne Bell. Such an individual should be mature (not necessarily old), easy to get along with, prompt in answering to the needs of others, and be willing to devote time to insuring that the group is well represented. [Side Note: The he/she construction above seems to be unnecessarily awkward; therefore, where the use of a pronoun seems appropriate, I shall use either he or she; however, the context should make the pronoun's referent clear. The gender of the person(s) referred to does not really matter.] The Group Coordinator should agree to the following conditions: 1) She will serve as long as she maintains the confidence of those being served and as long as she is willing. However, this period of service should be a minimum of three months, and she must provide at least 3 weeks notice before stepping down from the position. 2) He will maintain contact with the ACs and Sysops within the area in order to insure that (a) all boards are receiving net messages and net updates, (b) no board or group of boards becomes cut-off from the rest of the network. 3) She will listen to both sides of any disagreement and promote communication between the parties involved in the dispute. She will render an impartial recommendation based upon the facts and inform Wayne Bell of the dispute and recommended resolution in those instances where it appears that people may have strong and/or hurt feelings. This role calls for some maturity and judgement. Wayne should not be informed or bothered with the settlement of a dispute regarding a trivial matter, but he should be informed about all disputes which might have an unsettling effect upon the network. She may also recommend that the NC consider setting up a Problem Resolution Committee to deal with a particular grievance among sysops. Before doing so, the GC should contact both parties to the grievance and ascertain whether or not they would be willing to submit the grievance to such a process and whether or not they would agree to follow the recommendations of that committee. The responses of the individuals should be made known to the NC in the GC's report suggesting that such a procedure (PRC) is needed. 4) Promptness, Accuracy, Honesty, and Communications should be the qualities promoted by the Group Coordinator. The workings of the group (actually a mini-network) depend upon the Group Coordinator's being prompt in his responses, accurate in her work, honest in his dealings with others, and demonstrative of a willingness to communicate in an open and frank manner but with tact where it is called for. 5) He will appoint an Emergency or Assistant GC. The identity of the appointee will be made known to the NC. The assistant should obtain an account on Amber (the NC's board). If an emergency situation should arise or the GC go on an extended vacation, then the Assistant could be given access to the GC software and make network updates until the GC is able to return to his position. The Assistant is NOT automatically in line for the GC position. He might or might not be appointed as GC in the event that a replacement situation evolved. 6) Make the appointment of ACs or handle the election of the Area Coordinator as necessary. 7) Subscribe to and participate in Random's GC Sub. This sub is used by the GC's and the NC to discuss network policy, improvements to the network, removal of nodes for "cause", etc. The role of Group Coordinator may evolve in the future to take on additional responsibilities and there may be additional requirements. A GC may be removed from his position by the NC. Such removal would normally be because he was failing in his duties and responsibilities or has lost the confidence of the majority of ACs in his group. 4.2. Requirements for AC Prerequisites to be an Area Coordinator are: 1) Be currently running a system 24 hours a day. 2) Promise to run the system for at least 3 months into the future. 3) Promise to notify the GC at least 2 weeks in advance of taking down the system, and suggest a new coordinator for the area if/when resignation is tendered. If the GC follows the policy of holding elections then recommendation of a new AC is not required. 4) Be willing to put in some time to get the net up and keep it going within the area and be willing to promote WWIV to sysops in the area code. 5) Be willing to incur some LD charges. These long distance costs are often incurred in terms of maintaining contact with the nodes in the area to be sure that they are functioning correctly. If there is no AC in the area, you may confer with your GC who will help the boards in your area (once there are more than five) obtain an AC. Currently several methods exist in WWIVnet for the establishment of an AC in an area where there is none or where the previous AC left without recommending a replacement. These methods include: (1) nomination of an AC by the GC and ratification/refusal by the sysops in the area code; (2) nomination of an AC by the sysops in the area code and ratification or refusal by the GC. In any case, once an AC has been chosen for the area, Wayne Bell must still approve that person's acting as AC. It should be obvious from the guidelines in this manual, that the AC performs a valuable but somewhat thankless function and that there is no power associated with the position. Therefore, to attempt a coup in order to become AC would be somewhat meaningless. If an AC has power, it is because area boards have permitted the person to have power, NOT because the AC position is powerful. If the number of boards in an area that has an AC drops below five, the AC continues to function. The GC does not take over the responsibilities of AC unless the AC resigns. In that event, if there are fewer than five boards remaining in the area, the GC may fulfill the AC's duties until growth brings the number of systems to six or more. "There is one (and only one) coordinator per area code, and is/her primary duties are to assign net numbers to new systems joining the net, accept and check out connection info supplied by systems within their area code, and to forward this information (connection and bbs info changes) to @1." (WWIVnet Guide by Will Daystrom, (c) 1989 White Star Line Software) The quote above taken from WWIVnet Guide summarizes the primary duties of an AC very well. The only change in the description is that now the information is forwarded to the GC who in turn forwards it to 1 @1. The AC must assign net numbers to new systems that want to join the net. In addition to that primary duty, the WWIVnet Guide indicates that the area coordinator may under certain circumstances deny a network node number to a board. This should only be done in circumstances which are well-defined and those circumstances along with the reasons should be communicated to both the applicant and the GC. If an AC decides to have a policy regarding a waiting period to get on WWIVnet, that period should NOT exceed one week. An AC may be removed from his/her position by the GC or NC for failure to perform the duties and responsibilities of the position. If he has lost the confidence of those in the area code and the GC agrees with the need for removal from office, then the GC may recommend to the NC that the AC be removed from office. Only the NC can remove the AC. Removal from office should be a rare event. Sysops are NOT encouraged to turn the AC position into a political one. 5.0 Various Rules, Policies, Regulations, etc. Much of what is contained below has arisen due to various circumstances and the inclusion here is meant to help the sysop understand these matters. 5.1. Long Distance Connections It is NOT the AC's responsibility to establish long distance connections for the boards in the area code. That responsibility belongs to the sysop of each board. In many cases, however, several boards will use the long distance connections of one board which acts as a hub and which does most of the long distance polling. In that event, the long distance connection may limit the numbers of subs or mail sent by those which connect to him. Note that this is a function of the long distance connection and not a function of the AC (even if both are the same person). An AC may suggest that certain boards might wish to help another with long distance charges and so forth but remember that this is purely voluntary. Also an AC does not have the power to prohibit a person from making long distance connections or from taking certain subs. A sysop may make whatever long distance connections that he feels that he can afford and may carry any subs that he is willing to pay the long distance bill for. In cases where one board makes the long distance connections to obtain subs for others, the sysop of the board making the calls may limit the traffic, but that is him functioning as long distance connector not as AC. Further, the AC is not expected to provide technical advice regarding WWIVnet. It is nice if he can do so, but it is not part of the "job description." There are WWIV SUPPORT BOARDS which should be able to provide such advice if it is necessary. An AC, regardless of the software which he personally may be running is expected to recommend WWIV software for use by persons interested in joining WWIVnet. 5.2. Providing More Service An AC may choose to provide additional services to the area. For example, the AC may be instrumental in organizing meetings of local and/or area sysops and may help to organize the area for more effect long distance connections; however, this is not part of his function as an AC and should not be considered as part of the AC's authority. Any arrangements of this kind are accepted by area boards because they voluntarily choose to do so. They (the area boards) may at any time choose to do things differently and it should not affect the AC's duties. Thus, a word of caution to the AC, DO NOT BECOME EGO-INVOLVED in additional services and/or organizations. That is, always be certain that all understand that those activities are not part of your AC duties and that you can function as AC regardless of what transpires in the other circumstances. 5.3. Dissatisfaction with AC If you are dissatisfied with the performance of your AC, you should first discuss the matter with the AC. It may be that the AC has tired of his duties, is experiencing problems that you are unaware of, or is actually doing better than you know. In any case, the first step is to discuss the matter with the AC. If it cannot be resolved in this fashion, then you should make the GC aware of the problem. The GC should then check the matter with the AC. If you have not made the AC aware of your concerns, that fact will come to light at that time. Through a process of communication among sysops, AC, and GC it is hoped that the matter can be resolved. If not, the GC will discuss the matter with Wayne Bell who will have the final say in the matter. Communication, cooperation, and respect for one another are the keys to the successful resolution of problems. If necessary, the AC can be removed from the position by the NC. 5.4 The Group Coordinator (GC) The group Coordinator, upon receiving information for a new addition from an AC will put the information for bbslist into a file BBSLIST.XXX where the xxx is equal to 256 + the group number. For example, for group 5, this file would be BBSLIST.261. This information along with a CONNECT.xxx of the same number will be transmitted to 1 @1 who will update all master lists. The program that the Group Coordinator uses to send these updates to Wayne will be written by Wayne and provided to them. This insures the integrity of the network and will prevent 'rogue' groups from entering the network. If a Group Coordinator makes an error in his net update information, it will only affect his group. Thus problems can be isolated. 5.5 Net Editor Black Dragon (1@2380) developed the Net Editor to facilitate the updating of network files by sysops and Area Coordinators. That program is fully compatible with all network data structures since the beginning of WWIVNet to the present. An AC should ascertain whether or not his GC is prepared to handle updates in this format before using the program. 5.6. Sysops Sysops who decide to participate in WWIVnet should be aware that each host of a network sub has the right to insist upon her own rules, and she may delete any subscribing board that she wishes from the list of subscribers. Sysops who receive subs from other systems have the responsibility to restrict access to the sub according to the rules of the host. For example, some subs may limit access to User Number 1, to users with 255 access, or some other requirements such as all posts must not have tag lines. The receiving sysop must also take steps to inform users of the rules applying to a particular sub. GFILES are often a good way of doing this. These guidelines for sysops are nothing more than common sense and normal courtesy which reflect the desire on the part of all to cooperate in order to make the network work properly and efficiently. Sysops may choose to promote responsible use of the network by asking users to make their network posts conform to certain suggested guidelines. For example, the Sysop may request that users: o Not Use Foul language on the network o Not make personal attacks against others o Not post a lot of one-line messages on the network o Learn the differences between using A, W, or P to respond to network messages. These are merely suggestions for responsible use of the network and are not requirements; however, some of those suggestions are also found in the rules of the hosts of many network subs. Where they reflect the host rules, they are network rules for that sub. 5.7 Cost Containment Each sysop participating in WWIVnet should be sensitive to the cost involve in the network and should help to contain those costs. For most sysops, this involves things like (a) not sending junk mail to others, (b) awareness of and compliance with the rules in the appendices to this document regarding file transfers and so forth. Cost containment should be a concern anytime that someone else's long distance dollars are involved. A sysop who participates on more than one network should be very sensitive to using one network as a place to promote another. Such activities are generally discouraged except on subs which have been developed specifically for that purpose. Otherwise, the posting of announcements or any sort of advertisements in subs or email is generally discouraged UNLESS such information has been specifically requested by another sysop. Mass mailing through long distance connections of any type of advertisement is prohibitted. Sending another network's CONNECT.x, BBSLIST.x, etc., files through WWIVnet is also prohibitted. 5.8 Net Server Systems (1xxx nodes) A net server is defined as follows: A BBS dedicated to network connections and having no users. Exception to the no user rule is permitted if the users are limited to those who connect to the server and perhaps those who are seeking connection to the server. Generally, a server system should not have subs or transfer directories that would cause users to stay on the system for more than a few minutes. Again, exceptions are sometimes made for local or area sysop subs, transfer directory files directly related to the network such as (a) latest version of NETxx (b) latest copy of bbslist.* and connect.*. It is contrary to the purpose of a net server to try to be both a support board and a net server. If the limited support mentioned above begins to interfere with the net service function, the support services should be moved elsewhere. It is a recommended target goal that each net server have connections to 3 other servers which it pays from its own pocket and that it seek connections to 3 other servers where the other server sysop pays for the connection. This helps to spread the costs around. A net server may ask local sysops to share in the costs and may refuse to connect to them if they will not share in the costs. A net server should not charge LD sysops for use of the server as they are paying their LD charges to connect there. Sysops not sharing in the cost of the server may be forced to have their own LD connections if they wish to remain in the network. Sysops not sharing in the cost of the server may be prohibitted from having local connections to those who do share in the cost. The statements in the paragraph immediately above are PERMISSIVE but NOT required. That is, it is appropriate if such cost sharing arrangements are made, but it is not required that a server do this. Many servers are operated and paid for solely by the server sysop as a service to others. 6.0 Appendices 6.1 Appendix A - Network Policy for Illegal Activities 6.1.a Post from NC regarding Illegal Activities Mon Oct 15 20:39:31 1990 RE: WWIVnet Nothing illegal (pirating, phreaking, hacking, bank robbing, etc) shall be sent over the net. Violating this is cause for permanent removal from the network. This has ALWAYS been the policy, I just felt I should re-iterate it, in case anyone has forgotten. Now comes the new part: what happens locally on a system (that does not affect the network) is the business of that sysop, and is not an issue for the network. I am not advocating or approving of illegal acts. I am merely stating that what a sysop has on his system is for him to decide. As long as it does not affect the network, it is an issue only between that sysop and the police. I am saying that ACs or GCs are not responsible for policing the systems. That is a job for the police. ACs and GCs are volunteer positions (ie, no pay), and I'm sure everyone has better things to do with their time than to go on a witch hunt for pirated files. $F4 1@1 6.1.b Procedure to follow re Suspicion of Illegal Activities If a sysop believes that another sysop on the network is engaging in illegal activities, she should report the matter to her GC. The GC will discuss the matter with the other GCs and the NC and a "plan of action" will be determined. That plan may include notification of law enforcement officials and cooperation with them, or it may involve the suspension or removal of the offending node from the network. The point here is that the individual sysop may report the matter to the GC and be confident that the matter will not be dropped. 6.1.c Cooperation with Legal Authorities The NC and GCs will cooperate with legal authorities when asked to do so by these authorities. On occassion and if the situation warrants it, the NC and/or GC may contact legal authorities and report to them situations where illegal activities are suspected. 6.2 Appendix B -- Removal from the Network for "Cause" Removal from the Network for "Cause" means that the individual sysop has done something which necessitates, in the opinion of the GCs and NC, that the board be removed from the network for a period of time. The following procedures apply to a removal for "cause" and are designed to protect the rights of the individual sysop while preserving the right of network administrators to exercise their judgement to protect and preserve the network. 6.2a Steps in Removal for Cause or other Penalties 1) A GC or the NC will bring the issue up for discussion on the GC's sub. The GC may, at his discretion, call for an immediate vote on suspension from the network. This suspension is NOT the same thing as removal. It will be used in cases where the offense is so great that protection of the network calls for a suspension of the offending board until the issue is resolved. A suspension (in this case) does not mean that the board is removed from the network or that it has been found guilty of an offense; it merely means that in the collective judgement of the GCs, that board's activity needs to be cur- tailed until the matter has been investigated and a solution arrived at. Such suspensions should be rare events. 2) All GCs will have the opportunity to address the issue, call for additional investigation, etc. 3) A motion will be made and voted upon regarding the most appropriate treatment of the individual situation. Treatment may involve many things including but not limited to removal from the network for a stated time period. 4) Specific approval of the NC to the decision arrived at or a veto of that decision. 5) Communication of the final decision of the GCs and NC to the individual sysop. 6) Opportunity for appeal. If the individual sysop being removed believes that the GCs and NC were not in possession of relevant facts, he may present those facts to the NC and ask that the matter be reconsidered. The NC's decision on whether or not to grant additional reconsideration is final. 6.3 Appendix C -- Transfer of Files via the Network 6.3a General Policy WWIVnet is not designed for the transfer of files via e-mail or through subs. Such transmission may occur on occassion as part of a sub intended for another purpose. For example, the WWIV Modifications Net Sub is for the purpose of allowing sysops to share their mods. Occassionally a mod will be distributed in some form other than ASCII (ie as a pre-compiled file, an OBJ file, or some other format) and it may be UUencoded to facilitate the transmission via the network. Such occassional, irregular and infrequent occurances are NOT the subject of this policy. This policy is meant to apply to either the transmission of a large (bigger than 10k) file through the network or to a sub whose primary purpose is the transmission of uuencoded files. These situations (tranfer of large files and/or uuencoded subs) may only occur on WWIVnet through direct connections. That is, all members of the sub must connect directly to the host or, in the event of a transmission of a large file between two boards, these boards must connect directly to each other. In any other situation, the file should be sent as a regular upload by one sysop to the other sysop's board. Exceptions to this policy may be made only where the sysop obtains the approval of all intervening sysops. Exceptions to the policy should be rare and permission must be obtained in advance (not after the fact). 6.3b One Warning Where a sysop is found to violate the general policy regarding the sending of files through the network, one warning will be given. Further violation of the policy will be considered sufficient cause to remove the offending sysop(s) from WWIVnet. 6.4 Content of Network Transmissions Generally any legal material may be transmitted by WWIVnet. No one has the right to exercise censorship over what travels through the network. By this is meant that no sysop should follow the practice of reading the material passing through his board and deleting any of it. If a sysop does not want certain information passing through his board, he should ask the sysop for whom it is destined to find a different connection, but he should not try to delete the offending material. To delete the offending material from network packets would be contrary to network policy. To ask the sysops involved to find other connections would be appropriate. Deletion of information passing through your system may be justification for removal from the network "for cause." If you believe the material to be illegal, your duty is to notify the GC and provide proof. At that point, the GC and NC would handle the matter. How it would be handled would be a function of their judgement. 6.4a UUencoded Files An exception to this general rule is made for uuencoded files. If large amounts of uuencoded files are passing through your system and you have not given your permission for them to be sent, then you may delete them or otherwise prevent your system from paying any long distance charges that might be involved. Note that this rule does not have anything to do with the content of the files involved but rather deals with the format of the files. As a matter of courtesy, you should inform the originating system that you do not permit the transmission of these files. 6.4b "Adult" Subs Because of negative national publicity regarding BBSes and "porno- graphic materials," WWIVnet is instituting the following requirements and suggestions regarding hosts and subscribers to "Adult" subs. 6.4b.1 Not Auto-requestable As a matter of WWIVnet policy, adult subs may NOT be auto-requestable. The NC, or whomever may be in charge of policing the SUBS.LST, will not permit adult subs to carry the auto-requestable status. Hosts of adult oriented subs should NOT enable this feature in BOARDEDIT. 6.4b.2 Age Verification of Subscribing Sysops Hosts of adult subs are REQUIRED to verify the age of subscribing sysops by obtaining a notarized statement from the sysop attesting to his/her being an adult. Sysops are informed that adulthood is a function of state law and that the applicable state law is that of the originating system. Thus, if the host's system has a twenty-one year old age of majority for the purpose of obtaining "adult" materials, then the host should insist upon the subscriber's meeting that age requirement. A "sample" form suitable for use by a notary is contained later in this appendix. A sysop wishing to use his own form rather than the sample may do so. However, the host is responsibile for complying with this age verification requirement. 6.4b.3 Recommendation to Subscribing Sysops Sysops who subscribe to an "adult" sub are RECOMMENDED to use a form similar to that in appendix 6.4b.4 to verify the age of users permitted to access adult subs. While this age verification is a matter between the sysop and his users (i.e., this is not net policy), the simple fact is that each sysop is encouraged to take steps to insure that he/she is not subject to prosecution and that his/her equipment is protected against seizure by local law enforcement agencies. Requiring a notarized statement from users and keeping these statements on file will probably offer the greatest protection to the local sysop. 6.4b.4 Sample form for use by Host Sysop Sample Application for Subscribing to Adult Sub I, _______________________, am ____ years of age and have shown proof of (insert your name) my age to the notary who witnessed my signature. I hereby affirm my wish to subscribe to "adult subs" provided on bulletin boards via electronic transfers. I am aware that the material may be considered offensive, lewd, pornographic, or obscene by certain people and I agree to not hold the host responsible for such content. I further agree to inform the host of such "adult subs" if I decide to no longer subscribe to the sub or to permit my bulletin board or node number to be reassigned to others. ------------------------------------ ---------------- Signature Date I have witnessed the signature above and have examined an identification card bearing that individual's picture and indicating the individual's birthdate as __________________. _____________________ _____________ Notary Signature Date My commission expires ____________________. Date of expiration 6.4b.5 Sample form that a Sysop may wish to use for granting "adult" access. Application for adult access to ___________ BBS (Name of ) I, ____________________________________, am ________ years old. (print your name here) 1. I realize and fully understand that this application is for admittance to areas of _____ BBS that hold materials that are ADULT in nature, and that a great deal of the public may find these materials offensive in nature. Some are sexually explicit. Many of the conversations that take place in the various message areas (hereafter referred to as "subs") deal with sexually explicit and adult topics. 2. For reference, the areas on _____ BBS hereafter referred to as "adult areas" include, but are not limited to, file areas that contain pictures, stories, graphics, and images that are sexually-explicit in nature, including but not limited to fornication, fellatio, cunnilingus, sodomy, and other sexual activities, message bases that involve discussion of sexual topics, and games that deal with fornication, fellatio, cunnilingus, and other sexual activities. ALL MODELS ARE OVER THE AGE OF 18 YEARS! DO NOT ATTEMPT TO UPLOAD ANY FILES THAT FEATURE KIDDIE PORN, OR ANY OTHER ILLEGAL ACTIVITY. IF YOU DO, I ***WILL*** REPORT YOU TO THE FBI!!! THIS IS NOT DEBATABLE!!! I would just as soon you not upload any files to begin with.... 3. I understand that it is the policy of ____ BBS to restrict access to these areas (adult files and message areas) to those people that have a sincere desire for that access, and that they must be at least 18 years of age. Further, I certify that I do not find the adult sections of ____ BBS, and sexually- oriented material offensive, and that should I ever change my mind and become offended by any files obtained or messages read that I obtained from _____ BBS, that I will no longer call _____ BBS, and that I will inform the owner/operator of _____ BBS that I no longer wish access to the adult areas of ____ BBS. I will not press criminal or civil charges against the operator of _____ BBS if I find any messages, files, or games available on _____ BBS lewd, offensive, repulsive, questionable, or otherwise objection- able, nor for any other reason. I understand that the adult areas of ____ BBS for which I am requesting access are adult in nature, and that I am voluntarily assuming the risk that I may be offended by what may be obtained if this access is granted. 4. I will not give out my password and other logon information to anyone. I un- derstand that I will be held criminally liable for any laws that could be bro- ken by allowing a minor to use my account to gain access to the adult areas of ____ BBS. I further understand that this constitutes electronic tampering, and that pursuant to the Electronics Security Act of 1986, that I will be prosecuted if I am found guilty of doing so, and that I will be federally imprisoned, fined, or both. 5. I have not been solicited to call ____ BBS. I am doing so on my own free will. I agree to abide by all rules set forth by ____ BBS. I waive any and all claims for damage or loss caused from files/data that is obtained by me from _____ BBS. 6. I fully understand all of the above. I hereby waive all claims, civil and criminal now and forever that stem from my use of ____ BBS. Further, I understand that I will be prosecuted to the fullest extent of the law if it is discovered that I allow a minor to use my logon/accessibility so that said minor can obtain access to ____ BBS. Additionally, if I think that a minor has obtained my logon information, I will inform the operator of ____ BBS so that he may take appropriate measures to prevent any possible breech of security. 7. I am signing this with full knowledge that the penalty of perjury exists if any information is proven to be false. Print or type all information unless otherwise instructed. Name: ______________________________ (print) Address: ______________________________ ______________________________ ______________________________ Voice, home phone number: ( ) - Date of birth: _____ _____ ________ Month Day Year Write out the following statement in your own handwriting and sign it. "I hereby request access to the adult areas, as described in paragraph 2 above, of ____ BBS." __________________________________________ Signature Now you have two options. You may either 1), enclose a photocopy of your driver's license or military ID card as proof of your age, or you may take this entire application to a notary public and have it notarized. But you must do one or the other. Should you decide to have it notarized, the stan- dard notary information is provided: Notary: _____________________________, who appeared before me on ___________ and was duly sworn, signed this document in my presence. The person appeared to do so of their own free will and to be of sound mind. WITNESS my hand and official seal, this _______ day of _____________ 19_____. STATE OF _______________ COUNTY OF________________ _______________________________ Signature Notary State of________________ My commission expires____________________ UNDER NO CIRCUMSTANCES WILL ADULT ACCESS BE GRANTED TO ANYONE UNLES/UNTIL THIS FORM HAS BEEN SATISFACTORILY COMPLETED!!!!!! IF I DISCOVER THAT YOU ARE A MINOR, YOUR NAME WILL BE TURNED OVER TO THE PROPER AUTHORITIES FOR PROSECUTION! Mail to: [Your Name and address] 6.5 Registration 6.5.1 BBS Software A sysop who is using WWIV BBS software is expected to register that software in order to participate in WWIVnet beyond a 60-day "trial" period. Although registration is a prerequisite to continued participation on WWIVnet beyond the 60-day period, it is not to be considered a right. That is, even though a board is registered, it may still be dropped from WWIVnet "for cause." Registration may be accomplished by processing the REGISTER.FRM which is included in the WWIVxxx.ZIP archive. 6.5.2 Network Software If a sysop is using the WWIV network software to participate in WWIVnet but is not using the WWIV BBS software, then that sysop is expected to register the network software. This may be done by filling out the NETREG.FRM that is included in the NETxx.ZIP archive. 6.6 Part-Time Boards Prior to this version of the documentation, the admission of part-time boards was a function of the ACs policy for each area code. The policy regarding part-time boards on WWIVnet has been changed as follows: A part-time board may be a member of WWIVnet provided that the sysop of that board can obtain a connection. A part-time board is limited by policy to one connection in WWIVnet. A part-time board must comply with the registration requirements and must adhere to the phone number requirements discussed in the next section. 6.7 BBS Phone Numbers A bbs must list a legitimate BBS phone number in the BBSLISTings. Generally that phone number should be the phone number of that BBS; however, an exception is permitted in the case of private boards and/or part-time boards. Those boards are expected to also list a legitimate BBSes phone number; however, it may be the phone number of a different BBS. In the event that the phone number of a different bbs is given, that phone number must be for a WWIV BBS and the sysop's permission for such a listing must be obtained in advance. The GC must be notified of this arrangement. To summarize, it is against WWIVnet policy for a BBS to list a phone number that is false. Every phone number listed in the BBSLIST files must be for a legitimate WWIV bulletin board or for a bulletin board that does not run software associated with WWIV but that is participating in WWIVnet. 6.8 Procedure for an area code to change Groups For an area code to switch from one group to another is generally discouraged. However, such switching may occassionally be the best thing for both the area code and the network. The first step in the process is to ask the GC's permission to switch from your current group to another group. If the GC agrees to the switch and thinks it would be best for the network, your GC contacts the other GC and seeks his approval as well. If both GCs agree to the switch, then the member sysops of the area code are polled to determine whether or not 2/3rds of them wish to switch. If 2/3rds are in favor and if the GCs are in agreement, then the switch can be made with little effort. Any change of group by an area code will be announced and discussed on the GC sub prior to its taking effect. If, however, your GC does not agree to the swith OR if the switch is due to some sort of problem or conflict, then WWIVnet rules require that the problem or conflict first be addressed to ascertain whether or not it can be solved. No one in WWIVnet wishes to permit group switching if it helps to hide a problem for that hurts the entire network. If the problem cannot be worked out, then a poll of all members is conducted to determine whether or not a 2/3rds majority wishes to switch groups. In the event of a switching of groups, the new GC has the right to elect or appoint a different AC from the old one. New groups cannot be formed by anyone other than the NC and such formations will only occur after discussion among all GCs. 6.9 Pings The network software supports PINGS. Pings may be either generated by the software that you run on your BBS and/or by software that the author of the external program runs. A ping is a small request for information. If your BBS does not have the "matching" program, nothing will happen and you will get a short message in your log. If your BBS is running the "matching" program then a short message is sent to the author of the program letting him/her know that you are running that program. Authos who write programs that respond to or generate Pings should clear identify that fact in the documentation along with the type of information that is returned by the PING. 6.10 SubTypes Because WWIVnet had to renumber its nodes to accomodate changes made by the telephone companies, the method of identifying SubTypes must also change. The new rules are as follows: 6.10.1 Numeric subtypes may be used ONLY by those who had such subtypes before the conversion of node numbers. Those subtypes MUST REMAIN THE SAME; that is, they may not be switched to a new number and you may not add numeric subtypes for new subs. Any new sub MUST have an alphnumeric subtype. 6.10.2 New Subs must have alphanumeric subtypes. 6.10.3 You should examine the SUBS.LST and SUBS.x files to be sure that no one is using the Alphanumeric name that you wish to use for your sub. 6.10.4 Alphnumeric subtypes must be unique in the first 6 letters if you intend to have automatic responses generated. Automatic responses are files located in G-FILES that begin with SA and end with NET. The 6 letters (or less) following SA identify the response and should be the same as the subtype. It is up to you whether or not you try to make your subtypes identify your BBS as well as the subtype. All of the following would be examples of "legal" names for Subs: IRONID IRON01 01IRON I_01 I_02 11067A Questions regarding use of Subtypes may be directed to your GC, Random, or Filo.