Difference between revisions of "Feature:Multi-backend support"
(→Notes) |
|||
| Line 10: | Line 10: | ||
* https://xmpp.org/extensions/xep-0045.html | * https://xmpp.org/extensions/xep-0045.html | ||
| + | * https://help.hipchat.com/knowledgebase/articles/64377-xmpp-jabber-support-details | ||
Revision as of 18:48, 15 July 2015
Fact: a lot of people think we're crazy for using the IRC protocol as core transport.
Due to the limitations of IRC, as well as the potential cross-platform compatibility, it would generally make sense to add support for multiple protocols side-by-side. Which is actually not difficult, thanks to Sockethub abstracting protocol implementation and Hyperchannel only having to deal with Activity Streams.
With this, we could have an XMPP group chat running next to an IRC chat. Or it could even be a closed-source and centralized backends like Gitter, Slack, or Hipchat. As soon as we have support for multiple backends, we can then experiment and choose which one offers the best performance, features, and UX for Kosmos Pro.
If we add more platforms/protocols, we could also think about providing IRC gateways to those other ones.
