Update IS&T keytab request form link

[wiki.git] / doc / zephyr.mdwn

diff --git a/doc/zephyr.mdwn b/doc/zephyr.mdwn
index dc28947d2fd48d5ac28b0d67e26b9a37b6865608..6abd38e6eaa84bc73ad3c1f9b92879df1d985ae1 100644 (file)
--- a/doc/zephyr.mdwn
+++ b/doc/zephyr.mdwn
@@ -13,6 +13,8 @@ problem set.
 
 Zephyr is an underlying chat system; the built-in tools for exchanging messages via Zephyr are rudimentary. Most people who use Zephyr today take advantage of integrated clients that make the system easy to use.
 
+Here are [detailed instructions for getting onto Zephyr.](https://sipb.mit.edu/doc/zephyr-quick/)
+
 ## Major clients
 
 Here are some of the primary clients used at MIT. There's also a listing of [other Zephyr clients](http://zephyr.1ts.org/wiki/ZephyrClients), but their use is generally not recommended.
@@ -34,10 +36,11 @@ Roost makes use of [Webathena](https://webathena.mit.edu/) to keep you subscribe
 ### Zulip
 
 
-[Zulip](https://zulip.com/zephyr) is a web-based Zephyr client that also provides [mobile apps](https://zephyr.zulip.com/apps) for Android and iOS and desktop apps for Linux, Mac, and Windows. Zulip is developed by a company composed largely of MIT alums and SIPB members.
+[Zulip](https://zulipchat.com/zephyr) ([source code](https://github.com/zulip/zulip)) is a web-based Zephyr client that also provides [mobile apps](https://zephyr.zulipchat.com/apps) for Android and iOS and desktop apps for Linux, Mac, and Windows. Zulip was originally a proprietary product developed by a company composed largely of MIT alums and SIPB members. It was acquired by [Dropbox](https://www.dropbox.com/about) in 2014, and [released as open-source software](https://blogs.dropbox.com/tech/2015/09/open-sourcing-zulip-a-dropbox-hack-week-project/) a year later. The Zulip for Zephyr service is offered by [Tim Abbott](http://web.mit.edu/tabbott/www/) (MIT '06, SIPB member)'s Kandra Labs.
+
 Zulip, like Roost, is easy to set up because it uses Webathena for authentication.
 
-See [Zulip for MIT setup](http://zulip.com/zephyr) for details.
+See [Zulip for MIT setup](http://zulipchat.com/zephyr) for details.
 
 <!-- merge to http://zephyr.1ts.org/wiki/ZephyrClients (I would do this, except I can't log in…)
 
@@ -131,6 +134,14 @@ Some common classes include:
 > report what one is working on or up to, or ask friends questions, or
 > just rant about something.
 
+<strong>hello</strong>:
+> -c hello is for introducing yourself to the Zephyrsphere!
+> Send a zephyr to `-c hello -i YOUR_USERNAME` to let people
+> know you're a Zephyr user! This is a way to find out who else you know
+> uses Zephyr so you can subscribe to their class, and to get to know
+> new people through Zephyr. Also, feel free to invite others to
+> subscribe to your class!
+
 <strong>unclasses</strong>:
 > Most classes have an unclass, formed by prefixing "un" to the name. For
 > example, -c help has the unclass -c unhelp. The unclass is generally used for
@@ -190,6 +201,9 @@ phrases and words being thrown around.  Some of these include:
 > linking to the original source for reasons of privacy or discretion. "eiz"
 > means "Elsewhere in Zephyr", "eip" means "Elsewhere in Personals".
 
+<strong>eiw</strong>:
+> "Elsewhere in Webspace": instance used to comment on events on the Internet beyond Zephyr (like, say, on another messaging service).
+
 <strong>eim</strong>:
 > "Elsewhere in Meatspace": instance used to comment on events not on Zephyr.