Chrome should be able to generate certs

[wiki.git] / doc / szs.mdwn

diff --git a/doc/szs.mdwn b/doc/szs.mdwn
index 9cba19d1f4596b83612bbb98f6660ba3ac4f05b6..9d5a48d7d4543a85dd7d1abf1f6bb7f8ab90b351 100644 (file)
--- a/doc/szs.mdwn
+++ b/doc/szs.mdwn
@@ -1,4 +1,4 @@
-[[!meta title="Using SZS (the SMS to zephyr relay)"]]
+[[!meta title="Using SZS (the SMS to Zephyr Relay)"]]
 
 ## Introduction to SZS, the SMS to Zephyr Relay
 
@@ -58,17 +58,17 @@ Now find the line that starts with `filter personal` and edit it.
 Barnowl is picky about formatting, so here are some examples.
 This includes all your SMS <-> Zephyr messages in your personals and also colors your personal messages green.
 
-       filter personal -c green ( class ^szs$ ) or ( isprivate ^true$ and ( not type ^zephyr$ or ( class ^message$ ) ) ) or ( class kusername ) or ( type admin )
+       filter personal -c green ( class ^szs$ ) or ( isprivate ^true$ and ( not type ^zephyr$ or ( class ^message$ ) ) )
 
 To color all your SMS <-> Zephyr messages separately from your other personals messages, add another line that will override the coloring you gave it under the personal filter:
 
        filter szs -c cyan ( class ^szs$ ) or ( sender daemon.webzephyr@ATHENA.MIT.EDU )
 
-So you'll have general personals in one color, and SMS <-> Zephyr messages in a separate color, both of which appear when you hit '[Alt-p]'.
+So you'll have general personals in one color, and SMS <-> Zephyr messages in a separate color, both of which appear when you hit `[Alt-p]`.
 
 If you ever need to revert your personal filter, the default is:
 
-       isprivate ^true$ and (  not type ^zephyr$ or ( class ^message ) )
+       isprivate ^true$ and ( not type ^zephyr$ or ( class ^message ) )
 
 Now to reload your Barnowl configuration, in Barnowl, run
 
@@ -79,4 +79,4 @@ Therefore you could have multiple startup files if you wish. However, do note th
 ### Screen
 If you are going to regularly send and receive text messages using the Barnowl client for Zephyr, you will probably want a Barnowl instance running 24/7 so that whoever texts you won't encounter a `user not subscribed` error and so that your text message conversations don't disappear each time you quit Barnowl. 
 
-A good way to do this is to use screen and run it on the SIPB dialup machine, which allows you to run a Barnowl session within screen on the SIPB dialup machine that's theoretically up 24/7 (sadly outages do occur). See [UsingScreen](http://sipb-www.scripts.mit.edu/doc/wiki/UsingScreen) for more information; the basic idea is to `ssh` to `kusername@linux.mit.edu` and run `add kchen; owl-screen`, and in the future after `ssh`-ing to `kusername@linux.mit.edu` run 'screen -dr'.
+A good way to do this is to use screen and run it on the SIPB dialup machine, which allows you to run a Barnowl session within screen on the SIPB dialup machine that's theoretically up 24/7 (sadly outages do occur). See [UsingScreen](http://sipb-www.scripts.mit.edu/doc/wiki/UsingScreen) for more information; the basic idea is to `ssh` to `kusername@linux.mit.edu` and run `add kchen; owl-screen`, and in the future after `ssh`-ing to `kusername@linux.mit.edu` run `screen -dr`.