Article View: mod.announce.newusers
Article #39Changes to A Primer on How to Work With the Usenet Community
From: usenet
Date: Mon, 01 Dec 1986 05:22
Date: Mon, 01 Dec 1986 05:22
160 lines
8084 bytes
8084 bytes
*** old/etiquette.n Sat Nov 1 16:41:46 1986
--- src/etiquette.n Sat Nov 29 18:06:59 1986
***************
*** 2,4 ****
Expires: 40days
! Approved: spaf@gatech.CSNET
--- 2,4 ----
Expires: 40days
! Approved: spaf@gatech.EDU
***************
*** 5,7 ****
Original-from: chuq@sun.COM (Chuq Von Rospach)
! [Most recent change: 15 October 1986 by spaf@gatech.edu]
--- 5,7 ----
Original-from: chuq@sun.COM (Chuq Von Rospach)
! [Most recent change: 29 November 1986 by spaf@gatech.edu]
***************
*** 9,11 ****
A Primer on How to Work With the USENET Community
! Chuq Von Rospach (nsc!chuqui)
--- 9,11 ----
A Primer on How to Work With the USENET Community
! Chuq Von Rospach
***************
*** 16,20 ****
detailed technical documentation. This message describes the Usenet
! culture and customs which have developed over time. All new users should
! read this message to find out how Usenet works. *** *** (Old users could
! read it, too, to refresh their memories.) ***
--- 16,20 ----
detailed technical documentation. This message describes the Usenet
! culture and customs that have developed over time. All new users should
! read this message to find out how Usenet works. ***
! *** (Old users could read it, too, to refresh their memories.) ***
***************
*** 81,83 ****
what the article is about before they read it. A title like "Car for
! Sale" to net.auto does not help as much as "66 MG Midget for sale:
Beaverton OR." Don't expect people to read your article to find out what
--- 81,83 ----
what the article is about before they read it. A title like "Car for
! Sale" to rec.autos does not help as much as "66 MG Midget for sale:
Beaverton OR." Don't expect people to read your article to find out what
***************
*** 89,94 ****
! When you post an article, think about the people you are trying to reach.
! Asking UNIX(*) questions on net.auto will not reach as many of the people
! you want to reach as if you asked them on net.unix or net.unix-wizards.
! Try to get the most appropriate audience for your message, not the widest.
--- 89,95 ----
! When you post an article, think about the people you are trying to
! reach. Asking UNIX(*) questions on rec.autos will not reach as many
! of the people you want to reach as if you asked them on
! comp.unix.questions or comp.unix.wizards. Try to get the most
! appropriate audience for your message, not the widest.
***************
*** 102,105 ****
message to your local area. Some areas have special newsgroups with
! geographical limitations, and the newer versions of the news software
! allow you to limit the distribution of material sent to net-wide
newsgroups. Check with your system administrator to see what newsgroups
--- 103,106 ----
message to your local area. Some areas have special newsgroups with
! geographical limitations, and the recent versions of the news software
! allow you to limit the distribution of material sent to world-wide
newsgroups. Check with your system administrator to see what newsgroups
***************
*** 107,109 ****
! If you want to try a test of something, do not use a net-wide newsgroup!
Messages in misc.misc that say "This is a test" are likely to cause
--- 108,110 ----
! If you want to try a test of something, do not use a world-wide newsgroup!
Messages in misc.misc that say "This is a test" are likely to cause
***************
*** 111,115 ****
newsgroups that are local to your computer or area that should be used.
! Your system administrator can tell you what they are. There is a
! newsgroup called net.test, but it is there for the system administrators
! to use to test the network software and should not be used by anyone else.
--- 112,114 ----
newsgroups that are local to your computer or area that should be used.
! Your system administrator can tell you what they are.
***************
*** 133,140 ****
! Avoid posting messages to more than one newsgroup unless you are sure it
! is appropriate. If you do post to multiple newsgroups, do not post to
! each group separately. Instead, specify all the groups on a single copy
! of the message. This reduces network overhead and lets people who
! subscribe to more than one of those groups see the message once instead of
! having to wade through each copy.
--- 132,139 ----
! Avoid posting messages to more than one newsgroup unless you are sure
! it is appropriate. If you do post to multiple newsgroups, do not
! post to each group separately. Instead, specify all the groups on a
! single copy of the message. This reduces network overhead and lets
! people who subscribe to more than one of those groups see the message
! once instead of having to wade through each copy.
***************
*** 142,156 ****
! Certain newsgroups (such as net.jokes) have messages in them that may be
! offensive to some people. To make sure that these messages are not read
! unless they are explicitly requested, these messages should be encrypted.
! The standard encryption method is to rotate each letter by thirteen
! characters so that an "a" becomes an "n". This is known on the network as
! "rot13" and when you rotate a message the word "rot13" should be in the
! "Subject:" line. Most of the software used to read usenet articles have
! some way of encrypting and decrypting messages. Your system administrator
! can tell you how the software on your system works, or you can use the
! Unix command "tr [a-z][A-Z] [n-z][a-m][N-Z][A-M]". (Note that some versions
! of Unix don't require the [] in the "tr" command. In fact, some systems
! will get upset if you use them in an unquoted manner. The following should
! work for everyone, but may be shortened on some systems:
tr '[a-m][n-z][A-M][N-Z]' '[n-z][a-m][N-Z][A-M]'
--- 141,156 ----
! Certain newsgroups (such as rec.humor) have messages in them that may
! be offensive to some people. To make sure that these messages are
! not read unless they are explicitly requested, these messages should
! be encrypted. The standard encryption method is to rotate each
! letter by thirteen characters so that an "a" becomes an "n". This is
! known on the network as "rot13" and when you rotate a message the
! word "rot13" should be in the "Subject:" line. Most of the software
! used to read usenet articles have some way of encrypting and
! decrypting messages. Your system administrator can tell you how the
! software on your system works, or you can use the Unix command "tr
! [a-z][A-Z] [n-z][a-m][N-Z][A-M]". (Note that some versions of Unix
! don't require the [] in the "tr" command. In fact, some systems will
! get upset if you use them in an unquoted manner. The following
! should work for everyone, but may be shortened on some systems:
tr '[a-m][n-z][A-M][N-Z]' '[n-z][a-m][N-Z][A-M]'
***************
*** 183,185 ****
! One of the biggest problems we have on the network is that, when someone
asks a question, many people send out identical answers. When this
--- 183,185 ----
! One of the biggest problems we have on the network is that when someone
asks a question, many people send out identical answers. When this
Technical Details
Message-ID:
<7104@gatech.EDU>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!seismo!gatech!usenetShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!gatech!usenet From: usenet@gatech.EDU Newsgroups: mod.announce.newusers Subject: Changes to A Primer on How to Work With the Usenet Community Message-ID: <7104@gatech.EDU> Date: Mon, 1-Dec-86 00:22:51 EST Article-I.D.: gatech.7104 Posted: Mon Dec 1 00:22:51 1986 Date-Received: Mon, 1-Dec-86 20:23:17 EST Sender: spaf@gatech.EDU Lines: 160 Approved: spaf@gatech.EDU