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

From Kosmos Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
Fact: a lot of people think we're crazy for using the IRC protocol as core transport.
 
Fact: a lot of people think we're crazy for using the IRC protocol as core transport.
  
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.
+
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 not too hard, thanks to Sockethub abstracting protocol implementation and Hyperchannel only having to deal with Activity Streams.
  
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.
+
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, we should obviously also think about providing IRC gateways to those other ones, if possible.
+
If we add more platforms/protocols, we could also think about providing IRC gateways to those other ones.
  
 
== Notes ==
 
== Notes ==
  
* http://xmpp.org/extensions/xep-0045.html
+
* https://xmpp.org/extensions/xep-0045.html

Revision as of 00:03, 31 May 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 not too hard, 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.

Notes