Changes between Initial Version and Version 1 of Jabber


Ignore:
Timestamp:
Jan 17, 2010, 8:39:06 PM (11 years ago)
Author:
afarrell@mit.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Jabber

    v1 v1  
     1'''Jabber commands in barnowl'''
     2
     3A JID is a "Jabber Identification", which could be an individual user or a multi-user chat (MUC).
     4
     5'''jabberlogin'''
     6
     7 jabberlogin JID [password]
     8
     9If you're running barnowl on athena and want to log in to the mit.edu jabber server, you can probably just use the following command:
     10
     11 :jabberlogin username@mit.edu
     12
     13and your kerberos tickets will get passed along to the jabber server so that you don't have to enter your password.
     14
     15
     16'''jwrite'''<br />
     17
     18 jwrite JID [-t thread] [-s subject]
     19
     20Pressing j in barnowl will fill in the jwrite command for you, so typically, you'll jwrite to a JID by typing
     21
     22j username@mit.edu
     23
     24or
     25
     26j chatroom@conference.mit.edu
     27
     28Replying to jabber messages in barnowl is easily done by pressing r, which will start a jwrite command with the appropriate JID, whether for a user or a MUC.
     29
     30'''jmuc'''<br />
     31
     32 jmuc COMMAND ARGS
     33
     34jmuc commands: join, part, invite, configure, presence, presence -a
     35
     36jmuc is the command for dealing with MUCs in barnowl. You might use
     37
     38 :jmuc join <muc>
     39
     40to join a MUC.
     41                               
     42 :jmuc part <muc>
     43
     44to part (leave, stop getting messages from) a MUC. The MUC is taken from the current message if not supplied.
     45 
     46 :jmuc invite <jid> <muc>
     47
     48to invite that JID to that MUC. The MUC is taken from the current message if not supplied.
     49
     50 :jmuc configure <muc>
     51
     52to configure a MUC, which is necessary when setting up a new MUC; only the default configuration works for now, and the MUC is taken from the current message if it's not supplied in the command.
     53
     54 :jmuc presence <muc>
     55
     56to see the roster of JIDs in the MUC
     57
     58 :jmuc presence -a
     59
     60to see the rosters of JIDs for all the MUCs you're in at the time.
     61
     62
     63'''jroster'''<br />
     64
     65jroster COMMAND ARGS
     66
     67jroster is the command for dealing with your Jabber roster. Dealing with a Jabber roster lets you get notifications from Jabber servers about whether users are logged in, or when users log in or out, among other things.
     68
     69jroster commands: sub add unsub remove auth deauth
     70
     71 :jroster sub JID
     72
     73will ask that JID if you can subscribe to their presence. Unlike on zephyr, you allow users to know about whether you're logged in or not on a per-user basis, and they do the same for you.
     74
     75 :jroster add JID
     76
     77will add that JID to your roster without attempting to subscribe to their presence. This can be useful in the case of adding a shortname for a JID to your roster; see below for more information on that.
     78
     79 :jroster remove JID
     80
     81will unsubscibe you from presence information about that JID, and remove that JID from your roster
     82
     83 :jroster unsub JID
     84
     85will just unsubscribe from presence information about that JID.
     86
     87 :jroster auth JID
     88
     89and
     90
     91 :jroster deauth JID
     92
     93respectively authorize and deauthorize that JID to get presence information about you. If you get an OWL ADMIN message saying "Allow user (username@mit.edu) to subscribe to your presence? (Answer with the `yes' or `no' commands)", then, with the pointer on the message, you can use
     94
     95 :yes
     96
     97to authorize that JID as if you'd typed
     98
     99 :jroster auth username@mit.edu
     100
     101and similarly,
     102
     103 :no
     104
     105to deny that JID information about your presence.
     106
     107jroster argument flags: -g, -p, -n, and -a
     108
     109-g, -p, and -n work with only the add and sub commands
     110
     111-g is for adding a JID or JIDs to a group:
     112
     113 :jroster add JID [additional JIDs separated by spaces] -g group
     114
     115
     116-p is for purging a JID or JIDs from all groups:
     117
     118 :jroster add JID [additional JIDs separated by spaces] -p
     119
     120-n is for associating a JID with a short name:
     121
     122 :jroster add JID -n shortname
     123
     124the -n flag only works with one JID at a time.
     125
     126-a is for specifying which Jabber account the jroster command is for, in case you're logged into multiple Jabber accounts. The -a flag works with any of the jroster commands.
     127
     128 :jroster COMMAND JID1 -a JID2
     129
     130Would be what you would do when you want to add JID1 to the roster of your Jabber account JID2