Daniel Henninger wrote: > Actually then we are effectively talking about the same thing. "1" > means your client just informed you itself. 2 means your client AND > pyaim informed you via a message. 2 also could mean that your client > and the other person's jabber client informed you. 3 means all three > send you something. 0 means you don't even know there WAS an away message.
Yeah, we're close enough anyway...I read what you describe as "1" being that your (local) client prints the status (away) message in the text area of the window, possibly only after you send a message. This I would find to be annoying (only mildly, in the first case). I would also include in the "0" case any situation where you actually have to take action to view the status message. e.g. mouse over the contact in the roster for a tooltip, look at the roster where the status message is always underneath the username...and even cases where the status message is at the top of the chat window along with the username. -Alex Mauer "hawke" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature Url : http://modevia.com/pipermail/py-transports/attachments/20060317/4474bd30/signature.pgp From [EMAIL PROTECTED] Sat Mar 18 12:32:26 2006 From: [EMAIL PROTECTED] (James Bunton) Date: Sat Mar 18 12:32:40 2006 Subject: [py-transports] webreg 0.5 preview Message-ID: <[EMAIL PROTECTED]> Hi all. I've finally applied all the various fixes to webreg. It should work properly with PyMSNt 0.11 now. As well as with servers that use DNS SRV. If a few people confirm it works then I'll release it as a tarball on the website. Thanks :) svn co svn://delx.cjb.net/transportwebreg/trunk webreg --- James
