3 ms·

HipChat is known for having a problematic low-level protocol (based on a fork of XMPP), it's featureset is much more limited than Slack's, and it's implemented

HipChat is known for having a problematic low-level protocol (based on a fork of XMPP), it's featureset is much more limited than Slack's, and it's implemented in a different programming language. It'd be a lot less work to fork Slack and make it work on-premise than do something with HipChat. And that's saying a lot: forking Slack to make it run well on-premise would likely be an enormous project.

colordrops 8y ago
Or they could just leave it as is or rebrand it as Slack enterprise until they build a new version based on Slack.
- mulcahey 8y ago
  the UI/UX is so different I'd be very surprised if they managed that
  - edwinnathaniel 8y ago
    See SKYPE for Business. replace('Lync', 'Skype') probably...
    - nyconyco 8y ago
      Oh Mircosfot's strategy is the weirdest: OCS, Lync, Skype, Skype for Business, Teams, Yammer... People are just lost. Nayego is trying to hard build a HipChat-like client+server that is open source and based on XMPP. https://nayego.net/ https://nayego.net/ you can subscribe if you want to see a preview.