Huge problem for on-prem Hipchat customers. Plenty of customers out there not willing to put all their internal communications on the other side of their firewall, and now have to migrate. Slack doesn't have an on-prem option. Microsoft Teams doesn't have an on-prem option. What are enterprises supposed to use, RocketChat? Matrix? With no clear migration path? Really poor move on Atlassian's part. It would be one thi…
Mattermost CEO here. We're thinking of offering a special package for HipChat customers who want to stay on-prem using Mattermost. It's perhaps a mix of services, migration/import assistance and possibly a discount to our commercial version. Would such a package be interesting? For anyone who'd like to discuss outside of HN, please feel free to mail us at info at mattermost.com
Slack Is Buying HipChat from Atlassian
581–590 of 730 posts
Re: Slack Is Buying HipChat from Atlassian
#582Hey all here, So I observe that lots of team chat users seem lost and don't what to do anymore. The problem with alternative Open Source team chats attempts is that they are just another silo, or walled garden. Instances do not talk to each other. A private island cannot join continent. Even within the same organisations plenty of incompatible team chats are used competitively, fragmenting the workforces. We propose…
Does it run on an open protocol? (Maybe HTTP or XMPP based?)
Re: Slack Is Buying HipChat from Atlassian
#583Earlier quoted context omitted.
I don't see any compelling reason to adopt Slack. It does nothing that I care about that IRC doesn't do. If IRC completely implodes, I would run my own IRC server.
IRC is horrible on phones (shitty history when you drop out of an internet connection, no cross-device unread-count synchronization, no encryption or login, etc). There are add-ons that try to fix that, but it's still a giant pain. I personally love Riot and Matrix as a "modern IRC".
It does require having your own server to host it on though.
Re: Slack Is Buying HipChat from Atlassian
#584Hey all here, So I observe that lots of team chat users seem lost and don't what to do anymore. The problem with alternative Open Source team chats attempts is that they are just another silo, or walled garden. Instances do not talk to each other. A private island cannot join continent. Even within the same organisations plenty of incompatible team chats are used competitively, fragmenting the workforces. We propose…
Re: Slack Is Buying HipChat from Atlassian
#585Earlier quoted context omitted.
We do not use Slack, we use IRC for direct and fast communication. We do not use it for things that need RFCs and technical specifications, for that we use gitlab and other tools. IRC is great and I am using it for 14+ years already. It's stable, fast, efficient and secure with lots of options. I've written a lot of IRC bots in many languages because protocol is so easy and every language have library/bot for IRC tha…
What is the good story of multi-computer/mobile IRC access, with shared read state notifications? I used to run IRC on the server in the screen session, but this is unusable on mobile. And setting up properly was a total PITA.
Re: Slack Is Buying HipChat from Atlassian
#586Earlier quoted context omitted.
> There are two camps: the we-should-just-use-irc camp, and the we-need-every-feature camp. I'm firmly in the "email should be used for substantive discussions" camp, but ever since we got the bandwidth and CPU necessary for the internet to not be a primarily text-based medium, the illiterates took over and that was the end of that.
I'm firmly in the "email has no place in internal discussions whatsoever" camp. Tasks belong in tickets, long-term documentation/policies/meeting notes/etc belong in shared space (wiki), and discussions are faster and more productive in realtime (in-person, video call, or chat). E-mail might kick some of this off, or be used to schedule, but that should be it. The problem I think most people run into with the realtim…
Re: Slack Is Buying HipChat from Atlassian
#587Huge problem for on-prem Hipchat customers. Plenty of customers out there not willing to put all their internal communications on the other side of their firewall, and now have to migrate. Slack doesn't have an on-prem option. Microsoft Teams doesn't have an on-prem option. What are enterprises supposed to use, RocketChat? Matrix? With no clear migration path? Really poor move on Atlassian's part. It would be one thi…
Mattermost CEO here. We're thinking of offering a special package for HipChat customers who want to stay on-prem using Mattermost. It's perhaps a mix of services, migration/import assistance and possibly a discount to our commercial version. Would such a package be interesting? For anyone who'd like to discuss outside of HN, please feel free to mail us at info at mattermost.com
Re: Slack Is Buying HipChat from Atlassian
#588When is this overhype for Slack going to stop? It is a chat application with a slightly improved UI like it existed 30 years ago. This is a step in corporate IT that I really cannot fully understand. It seems that every company//startup has to use slack nowadays to pretend to be cool again. Everytime I have a serious conversation about the productivity gains or losses of Slack though, it is pretty clear to me that it…
Because just about every technical team needs the ability to do some sort of real-time communication, and Slack's UI is obviously better polished than the products that predate it (HipChat/IRC/etc). If you're looking for a product built by top MIT engineers who spent years thinking about how to make chat actually productive, check out Zulip. I'm one of those MIT engineers, and I agree that Slack is a huge waste of ti…
Re: Slack Is Buying HipChat from Atlassian
#589Earlier quoted context omitted.
Skype for Business, works on prem. Matrix is probably good too. Confluence can be installed on prem already.
S4B works with our VoIP infrastructure and is on-premise but the client is awfully slowly and badly needs to be reworked. But with Microsoft is abandoning on-premise services...