Difference between revisions of "Interop"

From XMPP WIKI
Jump to navigation Jump to search
Line 53: Line 53:
== 2010 Client Interop Participation ==
== 2010 Client Interop Participation ==


Each client instance listed has a ( local-part / password ) pair that should be configured on each server supporting C2S above. Except for mlinkrelease, because Kev doesn't want the possibility of using his server for spamming. Client devs, please ask Kev directly for mlinkrelease passwords.
Client developers are requested to ask server admins for usernames and passwords as required, to reduce the possibility of spamming (although it seems unlikely, it'd be a pest if it happened).


* [http://www.boldonjames.com BoldonJames]
* [http://www.boldonjames.com BoldonJames]
Line 60: Line 60:
*** Tony Richardson  [mailto:tony.richardson@boldonjames.com Mail]
*** Tony Richardson  [mailto:tony.richardson@boldonjames.com Mail]
** Clients
** Clients
*** SAFEchat V2.3 ( safechat / safechat )
*** SAFEchat V2.3


* [http://swift.im Swift]
* [http://swift.im Swift]
Line 67: Line 67:
*** Remko Tronçon [http://el-tramo.be/about#xmpp XMPP+EMail]
*** Remko Tronçon [http://el-tramo.be/about#xmpp XMPP+EMail]
** Clients
** Clients
*** Swift ( swift / swift )
*** Swift


* [http://gajim.org Gajim]
* [http://gajim.org Gajim]
Line 73: Line 73:
*** Yann Leboulanger [xmpp:asterix@jabber.lagaule.org XMPP]
*** Yann Leboulanger [xmpp:asterix@jabber.lagaule.org XMPP]
** Clients
** Clients
*** Gajim ( gajim / gajim )
*** Gajim


* [http://collabora.co.uk Collabora]
* [http://collabora.co.uk Collabora]
Line 81: Line 81:
*** (Emilio Pozuelo Monfort [xmpp:emilio.pozuelo@collabora.co.uk XMPP] — not actively working on the XMPP backend, but is writing a search UI which should be able to drive the XEP-0055 code in Gabble)
*** (Emilio Pozuelo Monfort [xmpp:emilio.pozuelo@collabora.co.uk XMPP] — not actively working on the XMPP backend, but is writing a search UI which should be able to drive the XEP-0055 code in Gabble)
** Clients
** Clients
*** [http://telepathy.freedesktop.org Telepathy-Gabble], as used by [http://live.gnome.org/Empathy Empathy] ( gabble / gabble )
*** [http://telepathy.freedesktop.org Telepathy-Gabble], as used by [http://live.gnome.org/Empathy Empathy]
** Particularly interested in testing (based on a quick show of hands on the developer channel):
** Particularly interested in testing (based on a quick show of hands on the developer channel):
*** XEP-0055  
*** XEP-0055  
Line 94: Line 94:
*** Nicolas Vérité [mailto:nverite@process-one.net Mail] = [xmpp:nverite@process-one.net IM]
*** Nicolas Vérité [mailto:nverite@process-one.net Mail] = [xmpp:nverite@process-one.net IM]
** Clients
** Clients
*** OneTeam ( oneteam / oneteam )
*** OneTeam


* [https://oneteam.im/ OneTeam for iPhone]
* [https://oneteam.im/ OneTeam for iPhone]
Line 100: Line 100:
*** Nicolas Vérité [mailto:nverite@process-one.net Mail] = [xmpp:nverite@process-one.net IM]
*** Nicolas Vérité [mailto:nverite@process-one.net Mail] = [xmpp:nverite@process-one.net IM]
** Clients
** Clients
*** OneTeam for iPhone ( iteam / iteam )
*** OneTeam for iPhone

Revision as of 13:51, 6 December 2010

XMPP Interop

Plan: to make this the main page for all Interop information, a work-in-progress

2010 Interop

From Monday 6th December through to Saturday 11th December, the XSF will be conducting an online interop event to test and demonstrate XMPP interoperability based on the latest core standards. Client and Server implementers are encouraged to participate.

There is a XEP-0045 chatroom hosted at interop@muc.xmpp.org - if anyone has interop problems connecting to it, this is known to be reachable from jabber.org accounts.

There is also a mailing list interop@xmpp.org - joining it can be done by sending email to interop-request@xmpp.org with a subject line of "subscribe", or alternately by using the Web Interface.

2010 Server Interop Participation

Each participating server has one IM domain, and a chatroom subdomain.

  • Isode
    • Contacts
    • Servers
      • mlinkrelease.xmpptest.com: R14.6 M-Link
      • mlinktrunk.xmpptest.com: R15.0 M-Link (trunk)
        • IPv4 and IPv6 dual-stack
  • Prosody
    • Contacts
    • Servers
      • Prosody 0.8.0, dev.prosody.im ports 5322 (c2s), 5369 (s2s)
  • ejabberd
    • Contacts
    • Servers
      • ejabberd21.xmpptest.com: ejabberd 2.1.x; dev2.process-one.net ; ports 5222 (c2s) 5269 (s2s) 5280 (BOSH); IBR with CAPTCHA
      • ejabberd master; just planned
  • psyced
    • Contacts
    • Servers
      • psyced - s2s only with XEP-0288 and D-W-D support in several configurations (xep-0178-enabled, standard dialback, dwd, bidi)
  • Tigase
    • Contacts
    • Servers
      • tigasetrunk.xmpptest.com: Tigase (trunk)

2010 Client Interop Participation

Client developers are requested to ask server admins for usernames and passwords as required, to reduce the possibility of spamming (although it seems unlikely, it'd be a pest if it happened).

  • Gajim
    • Contacts
      • Yann Leboulanger XMPP
    • Clients
      • Gajim
  • Collabora
    • Contacts
      • Sjoerd Simons XMPP
      • Will Thompson XMPP
      • (Emilio Pozuelo Monfort XMPP — not actively working on the XMPP backend, but is writing a search UI which should be able to drive the XEP-0055 code in Gabble)
    • Clients
    • Particularly interested in testing (based on a quick show of hands on the developer channel):
      • XEP-0055
      • XEP-0186 Invisible Command (deferred! how upsetting)
      • Non-Google implementations of google:queue
      • SOCKS5 bytestream proxies
      • Server PEP behaviour when we turn +notify on and off on the fly. Specifically: do updates that occur while we do not have +notify set get pushed to us when we turn it back on?
Retrieved from "https://wiki.xmpp.org/web/index.php?title=Interop&oldid=2269"