wiki:Jabber

Jabber commands in barnowl

A JID is a "Jabber Identification", which could be an individual user or a multi-user chat (MUC).

jabberlogin

jabberlogin JID [password]

If 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:

:jabberlogin username@mit.edu

and your kerberos tickets will get passed along to the jabber server so that you don't have to enter your password.

jwrite

jwrite JID [-t thread] [-s subject]

Pressing j in barnowl will fill in the jwrite command for you, so typically, you'll jwrite to a JID by typing

j username@mit.edu

or

j chatroom@conference.mit.edu

Replying 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.

jmuc

jmuc COMMAND ARGS

jmuc commands: join, part, invite, configure, presence, presence -a

jmuc is the command for dealing with MUCs in barnowl. You might use

:jmuc join <muc>[/<nick>]

to join a MUC (with a given nickname, or otherwise your JID).

:jmuc part <muc>

to part (leave, stop getting messages from) a MUC. The MUC is taken from the current message if not supplied.

:jmuc invite <jid> <muc>

to invite that JID to that MUC. The MUC is taken from the current message if not supplied.

:jmuc configure <muc>

to 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.

:jmuc presence <muc>

to see the roster of JIDs in the MUC

:jmuc presence -a

to see the rosters of JIDs for all the MUCs you're in at the time.

jroster

jroster COMMAND ARGS

jroster 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.

jroster commands: sub add unsub remove auth deauth

:jroster sub JID

will 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.

:jroster add JID

will 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.

:jroster remove JID

will unsubscibe you from presence information about that JID, and remove that JID from your roster

:jroster unsub JID

will just unsubscribe from presence information about that JID.

:jroster auth JID

and

:jroster deauth JID

respectively 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

:yes

to authorize that JID as if you'd typed

:jroster auth username@mit.edu

and similarly,

:no

to deny that JID information about your presence.

jroster argument flags: -g, -p, -n, and -a

-g, -p, and -n work with only the add and sub commands

-g is for adding a JID or JIDs to a group:

:jroster add JID [additional JIDs separated by spaces] -g group

-p is for purging a JID or JIDs from all groups:

:jroster add JID [additional JIDs separated by spaces] -p

-n is for associating a JID with a short name:

:jroster add JID -n shortname

the -n flag only works with one JID at a time.

-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.

:jroster COMMAND JID1 -a JID2

Would be what you would do when you want to add JID1 to the roster of your Jabber account JID2

Last modified 11 years ago Last modified on Jan 26, 2011, 1:31:27 AM