Just to double check, can you guys post which version of the transport you're using (revesion should be on the second line of yahoo.py)
Here is the transport version from yahoo.py: # $Id: yahoo.py,v 1.47 2006/08/24 13:33:50 normanr Exp $ version = 'CVS ' + '$Revision: 1.47 $'.split()[1] > I commented out the vanity address: > <!-- <host>jabberserver.uark.edu</host> --> Very strange, this should not have effected Exodus, but not Psi - maybe the transport restart fixed it? I suspect the transport restart fixed it. I have found that I can't always add a Yahoo user reliably in Exodus or Psi. Sometimes the Yahoo contact never gets the subscription request. However, when this happens I can log off the PyYIMt Transport, log back into the Transport and add the Yahoo contact and the Yahoo user does get the subscription request. > I changed the mainServerJID from > <mainServerJID>jabber.jabberserver.uark.edu</mainServerJID> > to > <mainServerJID>jabberserver.uark.edu</mainServerJID> This setting is only used to ignore service discovery requests for the confjid. > Another issue that I see in Psi is that when I bring up the Service > Discovery window "Yahoo Transport Chatrooms chat.yim" appears under the > "Yahoo! Transport entry. At the current time I am not using Yahoo Chatrooms > and I would rather not advertise something that is not enabled. How can I > get rid of "Yahoo Transport Chatrooms chat.yim" in the discovery window? > BTW I have commented out the <confjid> tag in my config.xml file. so based on the above logic, you need to set the mainServerJID to whatever JID the server uses to 'discover' support on each transport. With jabberd2 this would be 'jabberserver.uark.edu'. I am using jabberd2 and I have the <mainServerJID> set to the DNS name of the Jabber server which is 'jabberserver.uark.edu'. But I still see "Yahoo Transport Chatrooms chat.yim" in Psi and I just noticed that I also see "Yahoo Transport Chatrooms" in the Browser window in Exodus too. Sorry, I did not notice this is Exodus before. Is there something else I need to do so that disco does not show Yahoo chatrooms when I am not using them? > I am still seeing the "Unknown notify event: /presence/subscription" error > in the Exodus debug window when I add a yahoo user with Exodus but this may > be an Exodus problem. Does Psi have a debug window so I can compare the two > clients when adding a Yahoo user? Yes, right click your account entry, and select the XML Console, tick Enabled. Here is a snippet of debug XML from Exodus and Psi when I add a Yahoo contact. Notice the "Unknown notify event: /presence/subscription" error in the Exodus XML and notice that there is no such error in Psi. BTW even when I see the Unknown notify event in Exodus I can still sometimes add the Yahoo contact so this may be a mute point. Does it look like this error is being caused by bad XML in Exodus? BTW both of these XML statements are the last statements I see in the debug window of each client after I add a Yahoo contact. Exodus: <presence xmlns='jabber:client' to='[EMAIL PROTECTED]' from='[EMAIL PROTECTED]' id='229' type='subscribe'/> Unknown notify event: /presence/subscription Psi: <presence from="[EMAIL PROTECTED]" type="subscribed" id="168" to="[EMAIL PROTECTED]" /> On 9/19/06, Arnaud Ab?lard <[EMAIL PROTECTED]> wrote: > Les Seigneur wrote: > >> Here is another problem. When I am register with the Yahoo Transport it > >> looks like the registration is successful but the Yahoo Transport never > >> shows up in my Roster. > > I've also noticed that behavior lately.. actually it works smoothly for > a while then start acting like weirdly like this, then it works again > after a while. very strange. It's happy on my jabberd2 server. Just to double check, can you guys post which version of the transport you're using (revesion should be on the second line of yahoo.py) > When it doesn't work properly, the transport says the registration went > ok, but nothing shows up in the roster. When a registrered user tries to > log on the transport, it says ok, but for each contact the transport > gets a 404 cancel error: > > <iq xmlns='jabber:client' to='[EMAIL PROTECTED]/Gajim' > type='error' id='2935' > from='[EMAIL PROTECTED]'> > <vCard xmlns='vcard-temp'/> > <error code='404' type='cancel'> > <item-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/> > <text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'>The addressed JID or > item requested cannot be found.</text> > </error> > </iq> This is the broken vcard support showing up. It seems to be releated to avatar's. The code needs to be changed to return a 'valid' vcard even if there's no avatar for the user - and probably to broadcast the user's current avatar hash as part of the presence too. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ _______________________________________________ py-transports mailing list [email protected] http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
