[405] in BarnOwl Developers
Experience using owl as my primary jabber client
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Oct 29 18:05:48 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: Sun, 21 Jan 2007 17:04:56 -0500
I've been using owl as my primary jabber client for about a week.
For the most part it works well.
Things I've noticed/run into:
1) Jabber users expect your presence status to be up to date.
Typically clients do this by having idle timers and updating
between available, away and xa as time goes on. It's also common
for clients to change the priority as status changes. Jabber
users really expect your presence to be accurate. I've gotten
several complaints about being listed as online when not around
for hours. My girlfriend in particular has been grumpy about
this.
2) The lack of short name support is really frustrating as is the fact
that you have to specify -a on jwrite if you are logged into multiple
accounts. I think it's far more important to propose to send a
message (telling the user in the prompt which jid we've heuristically
selected) than to require -a.
3) I need to develop a better strategy for avoiding mixes when
involved in too many conversations. This is not a problem specific to
this project.
4) When jabber misbehaves i'd like a command to dump a serialized
message object out to a file for debugging.
--Sam
