Ah, i think it might be the JID case sensitivity issue again, was it ever merged?
I'm seeing that my roster sent testuser@ and i'm logged in with TestUser@ On Mon, Jun 1, 2009 at 4:58 PM, Gavin Mogan <halk...@gmail.com> wrote: > gav...@gavinm djabberd $ svn info > Path: . > URL: http://code.sixapart.com/svn/djabberd/trunk > Repository Root: http://code.sixapart.com/svn/djabberd > Repository UUID: 43dd9337-660f-0410-bd32-e7601923a1a1 > Revision: 867 > Node Kind: directory > Schedule: normal > Last Changed Author: mart > Last Changed Rev: 867 > Last Changed Date: 2009-04-29 16:54:32 +0000 (Wed, 29 Apr 2009) > > svn status doesn't seem to indicate any related files being changed > (got one in MUC, Authen/Pam, and a couple debugging lines in > DJabberd/djabberd) > On Mon, Jun 1, 2009 at 4:48 PM, Martin Atkins <m...@degeneration.co.uk> wrote: >> >> We did have some presence bugs related to this a long time ago, but I >> thought they were fixed now. You're running on trunk, or at least the latest >> stable release, right? >> >> Gavin Mogan wrote: >>> >>> How to reproduce: >>> >>> 1) Login to server using miranda jabber client >>> 2) Login to server with different connection (miranda again works, i >>> use psi for my tests though) >>> >>> >>> Client #2 doesn't see client #1 online until client #1 sends another >>> presence indicator. >>> >>> I've tried this with other combinations, and most of the time server >>> sends out a presence message on behalf of the other clients online on >>> your roster, but not miranda. >>> >>> Miranda: >>> <presence> >>> <priority>5</priority> >>> <c xmlns="http://jabber.org/protocol/caps" >>> node="http://miranda-im.org/caps" ver="0.7.9.0" ext="secureim mood" /> >>> <status></status> >>> </presence> >>> >>> PSI: >>> <presence> >>> <priority>5</priority> >>> <c xmlns="http://jabber.org/protocol/caps" >>> node="http://psi-im.org/caps" ver="0.12" ext="cs ep-notify html" /> >>> </presence> >>> >>> >>> I'm not really sure where to go from here, I tried to walk though but >>> I get lost in. I'm getting tempted to actually wrap every sub hit to >>> track the flow a bit to find out where things are going. >>> I'd appreciate some help debugging or a flow of how things work or >>> something. >> >> >