rfc1855.txt

RFC 的详细文档！

      posted to a specific group and that followups will go to
      that group.  Headers change this behavior.

    - Read all of a discussion in progress (we call this a thread)
      before posting replies.  Avoid posting "Me Too" messages,
      where content is limited to agreement with previous posts.
      Content of a follow-up post should exceed quoted content.

    - Send mail when an answer to a question is for one person only.
      Remember that News has global distribution and the whole world
      probably is NOT interested in a personal response.  However, don't
      hesitate to post when something will be of general interest to the
      Newsgroup participants.

    - Check the "Distribution" section of the header, but don't
      depend on it.  Due to the complex method by which News is
      delivered, Distribution headers are unreliable.  But, if you
      are posting something which will be of interest to a limited
      number or readers, use a distribution line that attempts to
      limit the distribution of your article to those people.  For
      example, set the Distribution to be "nj" if you are posting
      an article that will be of interest only to New Jersey readers.





Hambridge                    Informational                     [Page 11]

RFC 1855                 Netiquette Guidelines              October 1995


    - If you feel an article will be of interest to more than one
      Newsgroup, be sure to CROSSPOST the article rather than individually
      post it to those groups.  In general, probably only five-to-six
      groups will have similar enough interests to warrant this.

    - Consider using Reference sources (Computer Manuals, Newspapers,
      help files) before posting a question.  Asking a Newsgroup where
      answers are readily available elsewhere generates grumpy "RTFM"
      (read the fine manual - although a more vulgar meaning of the
      word beginning with "f" is usually implied) messages.

    - Although there are Newsgroups which welcome advertising,
      in general it is considered nothing less than criminal
      to advertise off-topic products.  Sending an advertisement
      to each and every group will pretty much guarantee your loss of
      connectivity.

    - If you discover an error in your post, cancel it as soon as
      possible.

    - DO NOT attempt to cancel any articles but your own.  Contact
      your administrator if you don't know how to cancel your post,
      or if some other post, such as a chain letter, needs canceling.

    - If you've posted something and don't see it immediately,
      don't assume it's failed and re-post it.

    - Some groups permit (and some welcome) posts which in other
      circumstances would be considered to be in questionable taste.
      Still, there is no guarantee that all people reading the group
      will appreciate the material as much as you do.  Use the Rotate
      utility (which rotates all the characters in your post by 13
      positions in the alphabet) to avoid giving offense.   The
      Rot13 utility for Unix is an example.

    - In groups which discuss movies or books it is considered essential
      to mark posts which disclose significant content as "Spoilers".
      Put this word in your Subject: line.  You may add blank lines to
      the beginning of your post to keep content out of sight, or you
      may Rotate it.

    - Forging of news articles is generally censured. You can protect
      yourself from forgeries by using software which generates a
      manipulation detection "fingerprint", such as PGP (in the US).

    - Postings via anonymous servers are accepted in some Newsgroups
      and disliked in others.  Material which is inappropriate when
      posted under one's own name is still inappropriate when posted



Hambridge                    Informational                     [Page 12]

RFC 1855                 Netiquette Guidelines              October 1995


      anonymously.

    - Expect a slight delay in seeing your post when posting to a
      moderated group.  The moderator may change your subject
      line to have your post conform to a particular thread.

    - Don't get involved in flame wars.  Neither post nor respond
      to incendiary material.

3.2    Administrator Guidelines

3.2.1 General Issues

    - Clarify any policies your site has regarding its subscription
      to NetNews groups and about subscribing to mailing lists.

    - Clarify any policies your site has about posting to NetNews
      groups or to mailing lists, including use of disclaimers in .sigs.

    - Clarify and publicize archive policy.  (How long are articles
      kept?)

    - Investigate accusations about your users promptly and with an
      open mind.

    - Be sure to monitor the health of your system.

    - Consider how long to archive system logs, and publicize your
      policy on logging.

3.2.2  Mailing Lists

    - Keep mailing lists up to date to avoid the "bouncing mail" problem.

    - Help list owners when problems arise.

    - Inform list owners of any maintenance windows or planned downtime.

    - Be sure to have "-request" aliases for list subscription and
      administration.

    - Make sure all mail gateways operate smoothly.

3.2.3. NetNews

    - Publicize the nature of the feed you receive.  If you do not get
      a full feed, people may want to know why not.




Hambridge                    Informational                     [Page 13]

RFC 1855                 Netiquette Guidelines              October 1995


    - Be aware that the multiplicity of News Reader clients may cause
      the News Server being blamed for problems in the clients.

    - Honor requests from users immediately if they request cancellation
      of their own posts or invalid posts, such as chain letters.

    - Have "Usenet", "Netnews" and "News" aliased and make sure someone
      reads the mail.

3.3 Moderator Guidelines

3.3.1 General Guidelines

    - Make sure your Frequestly Asked Questions (FAQ) is posted at
      regular intervals.  Include your guidelines for articles/messages.
      If you are not the FAQ maintainer, make sure they do so.

    - Make sure you maintain a good welcome message, which contains
      subscribe and unsubscribe information.

    - Newsgroups should have their charter/guidelines posted
      regularly.

    - Keep mailing lists and Newsgroups up to date. Post
      messages in a timely fashion.  Designate a substitute
      when you go on vacation or out of town.

4.0  Information Services (Gopher, Wais, WWW, ftp, telnet)

   In recent Internet history, the 'Net has exploded with new and varied
   Information services.  Gopher, Wais, World Wide Web (WWW), Multi-User
   Dimensions (MUDs) Multi-User Dimensions which are Object Oriented
   (MOOs) are a few of these new areas.  Although the ability to find
   information is exploding, "Caveat Emptor" remains constant.  For more
   information on these services, check references [14,28] in the
   Selected Bibliography.

4.1 User Guidelines

4.1.1. General guidelines

    - Remember that all these services belong to someone else.  The
      people who pay the bills get to make the rules governing usage.
      Information may be free - or it may not be!  Be sure you check.

    - If you have problems with any form of information service, start
      problem solving by checking locally:  Check file configurations,
      software setup, network connections, etc.  Do this before assuming



Hambridge                    Informational                     [Page 14]

RFC 1855                 Netiquette Guidelines              October 1995


      the problem is at the provider's end and/or is the provider's
      fault.

    - Although there are naming conventions for file-types used, don't
      depend on these file naming conventions to be enforced.  For
      example, a ".doc" file is not always a Word file.

    - Information services also use conventions, such as www.xyz.com.
      While it is useful to know these conventions, again, don't
      necessarily rely on them.

    - Know how file names work on your own system.

    - Be aware of conventions used for providing information during
      sessions.  FTP sites usually have files named README in a top
      level directory which have information about the files available.
      But, don't assume that these files are necessarily up-to-date
      and/or accurate.

    - Do NOT assume that ANY information you find is up-to-date and/or
      accurate.  Remember that new technologies allow just about anyone
      to be a publisher, but not all people have discovered the
      responsibilities which accompany publishing.

    - Remember that unless you are sure that security and authentication
      technology is in use, that any information you submit to a system
      is being transmitted over the Internet "in the clear", with no
      protection from "sniffers" or forgers.

    - Since the Internet spans the globe, remember that Information
      Services might reflect culture and life-style markedly different
      from your own community.  Materials you find offensive may
      originate in a geography which finds them acceptable.  Keep an open
      mind.

    - When wanting information from a popular server, be sure to use
      a mirror server that's close if a list is provided.

    - Do not use someone else's FTP site to deposit materials you
      wish other people to pick up.  This is called "dumping" and
      is not generally acceptable behavior.

    - When you have trouble with a site and ask for help, be sure to
      provide as much information as possible in order to help
      debug the problem.






Hambridge                    Informational                     [Page 15]

RFC 1855                 Netiquette Guidelines              October 1995


    - When bringing up your own information service, such as a homepage,
      be sure to check with your local system administrator to find what
      the local guidelines are in affect.

    - Consider spreading out the system load on popular sites by
      avoiding "rush hour" and logging in during off-peak times.

4.1.2 Real Time Interactive Services Guidelines (MUDs MOOs IRC)

    - As in other environments, it is wise to "listen" first to
      get to know the culture of the group.

    - It's not necessary to greet everyone on a channel or room
      personally.  Usually one "Hello" or the equivalent is enough.
      Using the automation features of your client to greet people is
      not acceptable behavior.

    - Warn the participants if you intend to ship large quantities
      of information.  If all consent to receiving it, you may send,
      but sending unwanted information without a warning is considered
      bad form just as it is in mail.

    - Don't assume that people who you don't know will want to talk to
      you.  If you feel compelled to send private messages to people you
      don't know, then be willing to accept gracefully the fact that they
      might be busy or simply not want to chat with you.

    - Respect the guidelines of the group.  Look for introductory
      materials for the group.  These may be on a related ftp site.

    - Don't badger other users for personal information such as sex, age,
      or location.  After you have built an acquaintance with another user,
      these questions may be more appropriate, but many people
      hesitate to give this information to people with whom they are
      not familiar.

    - If a user is using a nickname alias or pseudonym, respect that
      user's desire for anonymity.  Even if you and that person are
      close friends, it is more courteous to use his nickname.  Do