Added a "Zephyr Etiquette" section.

[wiki.git] / doc / UsingZephyr

diff --git a/doc/UsingZephyr b/doc/UsingZephyr
index 3be631e4815553cbc2685ce65185f8f37e8d232a..de24eee260db8ecc02e68bc4d2142414357bd5c7 100644 (file)
--- a/doc/UsingZephyr
+++ b/doc/UsingZephyr
@@ -96,6 +96,18 @@ If you spend enough time on Zephyr, you'll begin noticing some strange phrases a
 
 There are many other acronyms that are used; if you don't know what it means, try using the {{{whats foo}}} command at an Athena terminal. If you don't have the command, run {{{add sipb}}} first.
 
 
 There are many other acronyms that are used; if you don't know what it means, try using the {{{whats foo}}} command at an Athena terminal. If you don't have the command, run {{{add sipb}}} first.
 

+===Zephyr Etiquette===
+
+There are rules that people tend to use on Zephyr.  These include:
+
+Good grammar, spelling, and punctuation.  Not everybody uses capitalization, but they will still use good English.  Please do not say things such as "hey wut r u up to???".  It makes you look like an idiot.  Really.
+
+You don't need multiple question marks or exclamation points.  Usually.
+
+There are a few abbreviations people use, such as YMMV (Your Mileage May Vary) or IIRC (If I Remember Correctly).  Common abbreviations that you might find on AIM, however, are not.  People tend to look down upon "lol", "rofl", and other overly-used abbreviations.
+
+Don't sub randomly to someone's class who you just met on zephyr.  It is usually considered good form to wait until you've met the person in real life, or at least have had lengthy conversations with them in personals.
+

 === Startup ===
 
 There might be some options that you want to be consistent from session to session; you don't want to have to set the same variables each time.  You can fix this by adding the commands to your "startup" file, for example, {{{.owl/startup}}}.  This can be done from within Barnowl, by using the {{{startup}}} command:
 === Startup ===
 
 There might be some options that you want to be consistent from session to session; you don't want to have to set the same variables each time.  You can fix this by adding the commands to your "startup" file, for example, {{{.owl/startup}}}.  This can be done from within Barnowl, by using the {{{startup}}} command: