From: Jessica Hamrick <jhamrick@mit.edu>
Date: Sun, 14 Sep 2008 18:26:26 +0000 (-0500)
Subject: (no commit message)
X-Git-Tag: trac~223
X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/commitdiff_plain/a6c435d1aaf9f0c68111849ef0e7d10105d6e3dd?ds=sidebyside

---

diff --git a/doc/UsingZephyr b/doc/UsingZephyr
index d280697..b1010f9 100644
--- a/doc/UsingZephyr
+++ b/doc/UsingZephyr
@@ -64,6 +64,22 @@ For more documentation on the built-in commands and keybindings, you can press h
 
 === Classes and Instances ===
 
+Generall the most interesting discussion on Zephyr, however, happens on so-called Zephyr ''classes''. A class is a bit like a chat room in other IM systems. Anyone can send a zephyr to a class, and anyone who is subscribed to that class will receive it. There is no security on classes -- anyone who knows the name of a class can subscribe, and there is no way to determine who is subscribed to a given class.
+
+To subscribe to a class, use the subscribe command:
+
+{{{:subscribe CLASSNAME * *}}}
+
+To send a zephyr to a class, use the zwrite command with the -c option:
+
+{{{:zwrite -c CLASSNAME}}}
+
+Zephyrs to classes usually have an instance attached. An instance is a short “topic” or “subject” that indicates the context of a zephyr. Different instances are often used to multiplex multiple conversations on a high-traffic class. You can specify an instance with the -i option to zwrite:
+
+{{{:zwrite -c CLASSNAME -i INSTANCE}}}
+
+A message without an instance specified will default to the instance “personal”. 
+
 === Colors ===
 
 === Filters ===
\ No newline at end of file