Ticket #221 (new defect)

Hi,

yes, protocol-wise this seems like a bug. The required features are there (the last three).

Hi! Thanks for fast reply and <pre></pre>, I forgot about it. :)

Yes, it is strange, since the necessary features are there.

If you want to test yourself, register "disk.jabbim.cz" service and authorize the three contacts you will get.

By the way, web listing of  public@disk.jabbim.cz is at  http://disk.jabbim.cz/yourjid/ and  album@disk.jabbim.cz is at  http://album.jabbim.cz/yourjid/.

Found another contact, using old* Miranda:

<iq from="herjid" type="result" xml:lang="en" to="myjid" >
<query xmlns="http://jabber.org/protocol/disco#info">
<identity category="user" type="client" name="Miranda" />
<feature var="http://jabber.org/protocol/disco#info" />
<feature var="http://jabber.org/protocol/muc" />
<feature var="http://jabber.org/protocol/si" />
<feature var="http://jabber.org/protocol/si/profile/file-transfer" />
<feature var="http://jabber.org/protocol/bytestreams" />
<feature var="http://jabber.org/protocol/chatstates" />
<feature var="jabber:iq:agents" />
<feature var="jabber:iq:browse" />
<feature var="jabber:iq:oob" />
<feature var="jabber:iq:version" />
<feature var="jabber:x:data" />
<feature var="jabber:x:event" />
<feature var="vcard-temp" />
</query>
</iq>

* from jabber:iq:version

<name>Miranda IM 0.6.8 Unicode (Jabber v.0.6.0.2 [Miranda])</name>
<version>0.6.0.2</version>
<os>Windows Server 2003</os>

Newer Miranda is OK. When you look closely, old Miranda has wrong disco identity, Jabber Disk has a bit unusual identity…

Miranda 0.7.3 FT features work OK in SAPO:

<iq from="herjid" type="result" xml:lang="en" to="myjid" id="info6" >
<query xmlns="http://jabber.org/protocol/disco#info">
<identity category="client" type="pc" name="Miranda" />
<feature var="http://jabber.org/protocol/disco#info" />
<feature var="http://jabber.org/protocol/disco#items" />
<feature var="http://jabber.org/protocol/caps" />
<feature var="http://jabber.org/protocol/si" />
<feature var="http://jabber.org/protocol/si/profile/file-transfer" />
<feature var="http://jabber.org/protocol/bytestreams" />
<feature var="http://jabber.org/protocol/ibb" />
<feature var="jabber:iq:oob" />
<feature var="http://jabber.org/protocol/commands" />
<feature var="http://jabber.org/protocol/muc" />
<feature var="http://jabber.org/protocol/chatstates" />
<feature var="jabber:iq:last" />
<feature var="jabber:iq:version" />
<feature var="urn:xmpp:time" />
<feature var="urn:xmpp:ping" />
<feature var="jabber:x:data" />
<feature var="jabber:x:event" />
<feature var="vcard-temp" />
<feature var="jabber:iq:agents" />
<feature var="jabber:iq:browse" />
<feature var="http://jabber.org/protocol/mood+notify" />
<feature var="http://miranda-im.org/caps/secureim" />
<feature var="jabber:iq:privacy" />
<feature var="urn:xmpp:receipts" />
<feature var="http://jabber.org/protocol/tune+notify" />
</query>
</iq>

Weird.

Off-topic: nice to see PEP being deployed in the clients :)

I also have a contact with following client:

Client Name: Psi Client Version: 0.10 Operating System: Windows XP Capabilities:

Psi 0.10 can't do Entity Capabilities at all. Maybe SAPO MSG relies on caps (too much)? It should use normal disco#info when the opposite side can't do caps.

Ad Off-Topic: Yes, but nothing very useful yet… :/

We need to check if we fallback to pure disco#info if caps is not available.

Small update, info from Get Info:

public@disk.jabbim.cz (jdisk):
	Status: Online
	Status Message: "191.2MiB / 1.5GiB used, 1.3GiB free"
	Last Updated: 7/12/08 10:59 AM
	Capabilities:

As you can see, capabilities are empty.