Difference between revisions of "Feature:Multi-backend support"

Revision as of 18:05, 23 March 2015

Redirect to:

@@ Line 1: / Line 1: @@
-Fact: a lot of people think we're crazy for using the IRC protocol as core transport.
+#REDIRECT [[Feature2:Multi-backend support]]
-In the long run, it would probably make sense to add support for multiple protocols side-by-side. For example, why not have an XMPP group chat next to an IRC chat. That's what Sockethub is for after all. Could even be a Gitter channel or something other that is usually closed-source and centralized. And then we can choose which one offers the best performance and UX for Pro.
-Also, as we're building Hyperchannel as componentized app from the start, integrating different transport protocols isn't difficult in regards to the UI integration.
-If we add more, we should obviously also think about providing IRC gateways to those other ones, if possible.
-== Notes ==
-* http://xmpp.org/extensions/xep-0045.html