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

From Kosmos Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
Fact: a lot of people think we're crazy for using the IRC protocol as core transport.
+
Kosmos currently comes with support for both IRC and XMPP (albeit hiding most of their complexity from the user). With [http://sockethub.org/ Sockethub], it's very easy to add more protocols/APIs like for example [https://about.mattermost.com/ Mattermost] or [https://matrix.org/ Matrix], or even closed-source, centralized backends like Gitter, Slack, or Facebook Messenger.
  
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.
+
We could also think about providing open-protocol gateways/bridges to the non-open ones instead of implementing their API directly (or use existing ones where possible).
  
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.
+
Private servers/chat are planned to be implemented on top of XMPP, which is the most feature-complete (and extensible) messaging standard in existence today.
 
 
If we add more, we should obviously also think about providing IRC gateways to those other ones, if possible.
 
  
 
== Notes ==
 
== Notes ==
  
* http://xmpp.org/extensions/xep-0045.html
+
* https://xmpp.org/extensions/xep-0045.html
 +
* https://help.hipchat.com/knowledgebase/articles/64377-xmpp-jabber-support-details
 +
* https://slack.zendesk.com/hc/en-us/articles/201727913-Connecting-to-Slack-over-IRC-and-XMPP

Latest revision as of 10:06, 5 May 2017

Kosmos currently comes with support for both IRC and XMPP (albeit hiding most of their complexity from the user). With Sockethub, it's very easy to add more protocols/APIs like for example Mattermost or Matrix, or even closed-source, centralized backends like Gitter, Slack, or Facebook Messenger.

We could also think about providing open-protocol gateways/bridges to the non-open ones instead of implementing their API directly (or use existing ones where possible).

Private servers/chat are planned to be implemented on top of XMPP, which is the most feature-complete (and extensible) messaging standard in existence today.

Notes