[274] in BarnOwl Developers
short names, nicks and styles in jabber
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Oct 29 18:04:23 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
From: Sam Hartman <hartmans@MIT.EDU>
To: dirty-owl-hackers@mit.edu
Date: Tue, 31 Oct 2006 16:51:48 -0500
A lot of text jabber clients allow you to associate short names with
roster entries in order to make display easier. I think that combined
with associating short names with muc rooms could make the default
styles a lot simpler.
For example something like
jsipb/hartmans {hartmans@jis.mit.edu/laptop} 16:55
This is a MUC message
For a MUc room with short name jsipb and someone with a nick of
hartmans sending to the room. You don't need to say it's a jabber: it
only has one slash.
The thing in braces is the optional authenticated jid extension to the
MUC message, which you will not see with a jabber.mit.edu muc, but you
would see for example on jabber.ietf.org.
Alternatively you could put the authenticated jid in parens as you
would with a zsig.
I think it might be nice to set the owl class property to the short
name of the muc. If there is no short name, use the full muc name.
This would involve an extension to jjoin.
Actually, I think authenticated jid in place of zsig works better.
That way, you can use the braces for telling you which account it came
in on once we support multiple jabber accounts.
And then for personals something like
jabber from <shortname> time (jid)
or
jabber from <shortname> time (resource)
Again, using the long name if you have no short name on the roster.
Ideally, I'd like to get away from having owl know about jabber.
However I'm not sure how to do that and to have reasonable formatting
for personals.
