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

From Kosmos Wiki
Jump to navigation Jump to search
 
(One intermediate revision 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.
  
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.
+
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).
  
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.
+
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 platforms/protocols, we could also think about providing IRC gateways to those other ones.
 
  
 
== Notes ==
 
== Notes ==

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