X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/blobdiff_plain/1b7af0e5919199a293c4750fa95d512c4a89d142..163ac08c2a6c08b2475d45d2405bd321097c3715:/doc/szs.mdwn diff --git a/doc/szs.mdwn b/doc/szs.mdwn index fb88cb8..c76367f 100644 --- a/doc/szs.mdwn +++ b/doc/szs.mdwn @@ -6,7 +6,7 @@ This service relays messages between [Zephyr](http://sipb.mit.edu/doc/zephyr/) a ## Zephyr to SMS -To send zephyrs to a phone address as an Athena user, use your favorite zephyr client (see [Using Zephyr](http://sipb.mit.edu/doc/zephyr/) if you're not sure what this means) to zwrite `daemon/webzephyr.mit.edu` with a class of `szs` and an instance of `1234567890@servicemail.foo`; for instance, in Barnowl, +To send zephyrs to a phone address as an Athena user, use your favorite zephyr client (see [Using Zephyr](http://sipb.mit.edu/doc/zephyr/) if you're not sure what this means) to zwrite `daemon/webzephyr.mit.edu` with a class of `szs` and an instance of `1234567890@servicemail.foo`; for instance, in BarnOwl, ----> zwrite daemon/webzephyr.mit.edu -c szs -i 1234567890@servicemail.foo Hi imaginary friend, how are you doing? I'm sending you a text message through Zephyr. @@ -19,7 +19,7 @@ Do note that your message **will be accompanied by your phone number**! Messages over 140 chars will get **cut off** between the phone and Zephyr. The cell phone user will get an `invalidpducontent` error, although the first part of his/her message will get through to Zephyr. On the other hand, messages *from* Zephyr to cellphones can be as long as you like. -Also, hitting "`r`" in Barnowl to reply to a zephyrgram someone sent as a text message **does not work**. You'll have to hit `[Ctrl-R]` and typing out your friend's email address. (Afterward, you can scroll back to the last one you sent to your friend and hit "`r`", which will work). +Also, hitting "`r`" in BarnOwl to reply to a zephyrgram someone sent as a text message **does not work**. You'll have to hit `[Ctrl-R]` and typing out your friend's email address. (Afterward, you can scroll back to the last one you sent to your friend and hit "`r`", which will work). ### Personals When sending a zephyr from a phone, simply text a message to `kusername@szs.mit.edu` where `kusername` is the person's Athena username. @@ -47,7 +47,7 @@ Your message will appear like this: Zephyr replies to daemon/webzephyr.mit.edu -c szs -i 1234567890@servicemail.foo ) ### Filtering -As it turns out, for the same reasons that make replying to text messages such a pain, messages sent to Zephyr will appear in your personals (and can be viewed in Barnowl with the shortcut `[Alt-p]`) but messages you send in reply will not show up. This can make it annoying to carry on a conversation. To get text messages sent through Zephyr to show up in your personals (in Barnowl), you can edit your personal filter. To get your changes to persist across Barnowl sessions, you should directly edit your startup configuration file. This, by default, is the `startup` file in the `~/.owl` folder (where "~" stands for your home folder, so the full path should be something like `/mit/kusername/.owl/startup`). +As it turns out, for the same reasons that make replying to text messages such a pain, messages sent to Zephyr will appear in your personals (and can be viewed in BarnOwl with the shortcut `[Alt-p]`) but messages you send in reply will not show up. This can make it annoying to carry on a conversation. To get text messages sent through Zephyr to show up in your personals (in BarnOwl), you can edit your personal filter. To get your changes to persist across BarnOwl sessions, you should directly edit your startup configuration file. This, by default, is the `startup` file in the `~/.owl` folder (where "~" stands for your home folder, so the full path should be something like `/mit/kusername/.owl/startup`). So open up the "startup" file in your favorite text editor. If you're not sure which, try double-clicking the "startup" file, which should open it up in `gedit`. Or, if you're in a dialup ssh session, try `nano`. @@ -55,7 +55,7 @@ So open up the "startup" file in your favorite text editor. If you're not sure w Now find the line that starts with `filter personal` and edit it. -Barnowl is picky about formatting, so here are some examples. +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$ ) ) ) @@ -70,13 +70,13 @@ If you ever need to revert your personal filter, the default is: isprivate ^true$ and ( not type ^zephyr$ or ( class ^message ) ) -Now to reload your Barnowl configuration, in Barnowl, run +Now to reload your BarnOwl configuration, in BarnOwl, run :source ~/.owl/startup -Therefore you could have multiple startup files if you wish. However, do note that if you don't specify (overwrite) a filter in `startup2`, it will remain in its `startup` state. In other words, there is no original Barnowl filter configuration that your filters will revert to. +Therefore you could have multiple startup files if you wish. However, do note that if you don't specify (overwrite) a filter in `startup2`, it will remain in its `startup` state. In other words, there is no original BarnOwl filter configuration that your filters will revert to. ### 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. +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 [Using Screen](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 [Using Screen](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`.