From d5f8fc301096e9fbfb4664717f5c634c04001f23 Mon Sep 17 00:00:00 2001 From: Brian Chen Date: Mon, 19 Oct 2015 16:07:12 -0400 Subject: [PATCH] more slang, class derivatives, zcrypt link, em dashes --- doc/zephyr.mdwn | 63 ++++++++++++++++++++++++++++++++++++------------- 1 file changed, 46 insertions(+), 17 deletions(-) diff --git a/doc/zephyr.mdwn b/doc/zephyr.mdwn index 4798513..eea177c 100644 --- a/doc/zephyr.mdwn +++ b/doc/zephyr.mdwn @@ -63,9 +63,9 @@ Generally the most interesting discussion on Zephyr 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 +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. +given class. (For secure or private zephyring, consider [[zcrypt]].) To subscribe to a class, use the subscribe command: @@ -90,11 +90,20 @@ You can send zephyrs to individuals (as opposed to classes) with: :zwrite USERNAME +It is possible to `zwrite` to multiple individuals at once, by listing the +usernames separated by spaces: + + :zwrite USERONE USERTWO USERTHREE + +When doing this, it is customary to include the line `CC: USERONE USERTWO +USERTHREE` in the body of the zephyr, although this is not required or +enforced. + ### Aside: zephyr triplets -All messages are actually sent to a "zephyr triplet" -- a class, instance, and recipient. Subscriptions are also made to zephyr triplets. The recipient can be either "*" -- to indicate a broadcast message -- or a specific individual. +All messages are actually sent to a "zephyr triplet" — a class, instance, and recipient. Subscriptions are also made to zephyr triplets. The recipient can be either "*" — to indicate a broadcast message — or a specific individual. -When sending, the default class is "message", instance is "personal", and recipient is "*". `zwrite` supports sending to arbitrary triples with `:zwrite -c CLASS -i INSTANCE USERNAME` -- the two examples above use the defaults for the parts that aren't specified. +When sending, the default class is "message", instance is "personal", and recipient is "*". `zwrite` supports sending to arbitrary triples with `:zwrite -c CLASS -i INSTANCE USERNAME` — the two examples above use the defaults for the parts that aren't specified. For subscriptions, the class must be specified. You can specify all instances on a class with "\*", or specify just one instance. You can only sub to recipient "\*" or your own personals (indicated by "%me%").) @@ -122,6 +131,19 @@ Some common classes include: > report what one is working on or up to, or ask friends questions, or > just rant about something. +unclasses: +> 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 +> snarky or unproductive replies; the prototypical example that first inspired +> their creation was telling somebody with computer issues to run +> `sudo rm -rf /`. Rarely, un- prefixes are stacked for even snarkier +> discussion, on -c ununhelp and so on. + +.d classes: +> Classes like -c help.d are sometimes used for discussions that deviate from +> the conversation on the main class. .d instances are more common, though; +> see below. + ### Zephyr Slang If you spend enough time on Zephyr, you'll begin noticing some strange @@ -138,14 +160,9 @@ phrases and words being thrown around. Some of these include: > person, they will send another Zephyr to that wrong/class person > simply saying "mix". This basically just means, "oops, sorry, I > didn't mean to send that Zephyr here". You might also see "-i mix", -> which is the same thing, only with instances. - -.d: -> You may see an instance change from `-i foo` to `-i foo.d`. This -> indicates a deviation or tangent from the the original topic. - -.q: -> Simiarly, `.q` at the end of an instance name indicates a quote. +> which is the same thing, only with instances. The specific invocation "unmix" +> is used when accidentally sending a Zephyr to a class instead of its unclass +> or vice versa. to Stark: > To answer a question or replying to a topic to a topic several hours @@ -154,6 +171,13 @@ phrases and words being thrown around. Some of these include: > without seeing if anyone had answered yet, or worse, if the instance > had moved on to an entirely different topic. +.d: +> You may see an instance change from `-i foo` to `-i foo.d`. This +> indicates a deviation or tangent from the the original topic. + +.q: +> Similarly, `.q` at the end of an instance name indicates a quote. + ttants: > Literally, "Things That Are Not The Same". @@ -166,12 +190,17 @@ phrases and words being thrown around. Some of these include: > means "Elsewhere in Zephyr", "eip" means "Elsewhere in Personals". eim: -> "Elsewhere in Meatspace"; instance used to comment on events not on Zephyr. +> "Elsewhere in Meatspace": instance used to comment on events not on Zephyr. + +doxp: +> "Do X predicate", from Lisp naming convention. A discussion on whether one +> should do X. -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. Alternatively, running the single command -`athrun sipb whats foo` works as well. +Many of the acronyms may be suffixed onto normal instance topics with a period +to indicate relation. 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. Alternatively, running the +single command `athrun sipb whats foo` works as well. ### Zephyr Etiquette -- 2.44.0