<div dir="ltr"><div dir="auto"><div>Why did you just ignore the answer when I sent it? <br><div dir="auto"><br><a href="https://matrix.org/docs/guides/faq.html#what-is-the-difference-between-matrix-and-xmpp">https://matrix.org/docs/guides/faq.html#what-is-the-difference-between-matrix-and-xmpp</a><br></div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">What is the difference between Matrix and XMPP?</div><div dir="auto"><br></div><div dir="auto">The Matrix team used XMPP (Openfire, ejabberd, spectrum, asmack, XMPPFramework) for IM before starting to experiment with open HTTP APIs as an alternative in around 2012. The main issues with XMPP that drove us in this direction were:</div><div dir="auto"><br></div><div dir="auto"> Not particularly web-friendly - you can’t easily speak XMPP from a web browser. (N.B. Nowadays you have options like XMPP-FTW and Stanza.io that help loads with letting browsers talk XMPP).</div><div dir="auto"> Single logical server per MUC is a single point of control and availability. (MUCs can be distributed over multiple physical servers, but they still sit behind a single logical JID and domain. FMUC improves this with a similar approach to Matrix, but as of Oct 2015 there are no open source implementations.)</div><div dir="auto"> History synchronisation is very much a second class citizen feature</div><div dir="auto"> Bridging to other protocols and defragmenting existing communication apps and networks is very much a second class citizen feature</div><div dir="auto"> Stanzas aren’t framed or reliably delivered without extensions. (See <a href="http://wiki.xmpp.org" target="_blank">wiki.xmpp.org</a> for an XMPP take on this)</div><div dir="auto"> Multiple device support is limited. (Apparently Carbons and MAM help with this)</div><div dir="auto"> Baseline feature set is so minimal that fragmentation of features between clients and servers is common, especially as interoperability profiles for features have fallen behind (as of July 2015)</div><div dir="auto"> No strong identity system (i.e. no standard E2E PKI, unless you count X.509 certs, which are questionable)</div><div dir="auto"> Not particularly well designed for mobile use cases: push; bandwidth-efficient transports. (Since the time of writing a Push XEP has appeared, and <a href="http://wiki.xmpp.org" target="_blank">wiki.xmpp.org</a> claims that XMPP runs “fine” over a 9600bps + 30s latency link.)</div><div dir="auto"><br></div><div dir="auto">The whole subject of XMPP vs Matrix seems to bring out the worst in people. Rather than fighting over which open interoperable communication standard works the best, we should just collaborate and bridge everything together. The more federation and interoperability the better.</div><div dir="auto"><br></div><div dir="auto">We think of Matrix and XMPP as being quite different; at its core Matrix can be thought of as an eventually consistent global JSON db with an HTTP API and pubsub semantics - whilst XMPP can be thought of as a message passing protocol. You can use them both to build chat systems; you can use them both to build pubsub systems; each comes with different tradeoffs. Matrix has a deliberately extensive ‘kitchen sink’ baseline of functionality; XMPP has a deliberately minimal baseline set of functionality. If XMPP does what you need it to do, then we’re genuinely happy for you :) Meanwhile, rather than competing, an XMPP Bridge like Skaverat’s xmpptrix beta or jfred’s matrix-xmpp-bridge or Matrix.org’s own purple-matrix has potential to let both environments coexist and make the most of each other’s benefits.</div></blockquote><div dir="auto"><br><br><a href="https://matrix.org/docs/guides/faq.html#what-is-the-difference-between-matrix-and-irc" target="_blank">https://matrix.org/docs/<wbr>guides/faq.html#what-is-the-<wbr>difference-between-matrix-and-<wbr>irc</a><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto">What is the difference between Matrix and IRC?</div><div dir="auto"><br></div><div dir="auto">We love IRC. In fact, as of today the core Matrix team still uses it as our primary communication tool. Between us we’ve written IRCds, IRC bots and admined dreamforge, UnrealIRCd, epona, ircservices and several others. That said, it has some limitations that Matrix seeks to improve on:</div><div dir="auto"><br></div><div dir="auto"> Text only</div><div dir="auto"> No history</div><div dir="auto"> No multiple-device support</div><div dir="auto"> No presence support</div><div dir="auto"> Fragmented identity model</div><div dir="auto"> No open federation</div><div dir="auto"> No standard APIs, just a rather limited TCP line protocol</div><div dir="auto"> Non-standardised federation protocol</div><div dir="auto"> No built-in end-to-end encryption</div><div dir="auto"> Disruptive net-splits</div><div dir="auto"> Non-extensible</div><div dir="auto"><br></div><div dir="auto">IRCv3 exists and is addressing some of these issues; this is great news and we wish them well. It’s almost a contradiction in terms to get competitive between openly interoperable communication projects - we look forward to increasing the richness of Matrix<->IRC bridges as the project progresses.</div></div></blockquote><div class="gmail_extra"><br><div class="gmail_quote">On Jul 8, 2017 1:47 PM, "Big Smile" <<a href="mailto:big.smile@openmailbox.org" target="_blank">big.smile@openmailbox.org</a>> wrote:<br type="attribution"><blockquote class="gmail-m_-3712165176006435496quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Can't understand why they don't use XMPP and participate in XEP<br>
writting. This look like an another "not invented here" driven project.<br>
:(<br>
<div class="gmail-m_-3712165176006435496elided-text">______________________________<wbr>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.hackerspaces.org" target="_blank">Discuss@lists.hackerspaces.org</a><br>
<a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.hackerspaces.org/<wbr>mailman/listinfo/discuss</a><br>
</div></blockquote></div><br></div></div></div>
</div>