I agree. With which server/version did you test?

> With which server/version did you test?

I tested jabber.org, im.apinc.org and amessage.de.

http://www.xmpp.org/extensions/xep-0079.html#process-s2s-disco
> If a server supports Advanced Message Processing, it MUST report that by
> including a service discovery feature of "http://jabber.org/protocol/amp" in
> the service discovery information result that it returns to the requesting
> entity.

And unfortunately I did not get this feature in any of theses 3 servers:

== SEND ==

<iq from='alice@im.apinc.org/Psi'
    to='im.apinc.org'
    type='get'>
  <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>

== RECV ==

<iq from="im.apinc.org" type="result" to="alice@im.apinc.org/Psi" >
<query xmlns="http://jabber.org/protocol/disco#info">
<feature var="jabber:iq:privacy" />
<feature var="jabber:iq:time" />
<feature var="jabber:iq:last" />
<feature var="jabber:iq:version" />
<feature var="jabber:iq:browse" />
<feature var="stringprep" />
<feature var="fullunicode" />
<feature var="xmllang" />
<feature var="http://jabber.org/protocol/disco#info" />
<feature var="http://jabber.org/protocol/disco#items" />
<identity category="server" type="im" name="Apinc Jabber Server" />
<feature var="http://jabber.org/protocol/offline" />
<feature var="msgoffline" />
<feature var="urn:xmpp:ping" />
<feature var="jabber:iq:register" />
</query>
</iq>


I don't know whether a real Jabber server implement this.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/6.