Difference between revisions of "Interop"

From XMPP WIKI
Jump to navigation Jump to search
(5 intermediate revisions by the same user not shown)
Line 37: Line 37:
** Servers
** Servers
*** psyced - s2s only with XEP-0288 and D-W-D support in several configurations (xep-0178-enabled, standard dialback, dwd, bidi)
*** psyced - s2s only with XEP-0288 and D-W-D support in several configurations (xep-0178-enabled, standard dialback, dwd, bidi)
* [http://www.tigase.org Tigase]
** Contacts
*** Florian Jensen [mailto:admin@flosoft.biz Mail] [xmpp:admin@im.flosoft.biz IM]
** Servers
*** Tigase (trunk)


== 2010 Client Interop Participation ==
== 2010 Client Interop Participation ==
Line 53: Line 59:
** Clients
** Clients
*** Swift
*** Swift
* [http://gajim.org Gajim]
** Contacts
*** Yann Leboulanger [xmpp:asterix@jabber.lagaule.org XMPP]
** Clients
*** Gajim
* [http://collabora.co.uk Collabora]
** Contacts
*** Sjoerd Simons [xmpp:sjoerd.simons@collabora.co.uk XMPP]
*** [[User:Wjt|Will Thompson]] [xmpp:will.thompson@collabora.co.uk XMPP]
*** (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
*** [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):
*** 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?
* [https://oneteam.im/ OneTeam]
** Contacts
*** Nicolas Vérité [mailto:nverite@process-one.net Mail] = [xmpp:nverite@process-one.net IM]
** Clients
*** OneTeam
* [https://oneteam.im/ OneTeam for iPhone]
** Contacts
*** Nicolas Vérité [mailto:nverite@process-one.net Mail] = [xmpp:nverite@process-one.net IM]
** Clients
*** OneTeam for iPhone

Revision as of 14:43, 3 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.

2010 Server Interop Participation

  • Isode
    • Contacts
    • Servers
      • R14.6 M-Link
      • R15.0 M-Link (trunk)
  • Prosody
    • Contacts
    • Servers
      • Prosody 0.8.0, dev.prosody.im ports 5322 (c2s), 5369 (s2s)
  • ejabberd
    • Contacts
    • Servers
      • 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
      • Tigase (trunk)

2010 Client Interop Participation

  • 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?