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…
This shows one strength of open source where you have the option to fork and maintain your own solution in the case the project heads the wrong way. Unfortunately the whole world seems to be heading the wrong way with cloud based "everything as a service" where you control nothing. If the provider or cloud goes down you have nothing. Even if they just take your keys you have nothing. It's quick and easy to setup and…
Slack Is Buying HipChat from Atlassian
561–570 of 730 posts
Re: Slack Is Buying HipChat from Atlassian
#562 Taking out a competitor is good for Slack, said Butterfield: “There’s fewer choices for people.”
What a statement! This is why I dislike Slack as a company and as much as I hate Teams (have to use it at work), I have no problem with it if the choice is Slack or Teams.Re: Slack Is Buying HipChat from Atlassian
#563- RocketChat - OTR breaks very easily, and https://github.com/RocketChat/Rocket.Chat/pull/10094 has been open for months - Matrix / Riot - Last I tried it had the most complex and unusable interface - Mattermost - At first glance seems to include E2E, but when reading a little bit more...not really, just at rest encryption - https://mattermost.atlassian.net/browse/MM-669 - Zulip - nop - https://github.com/zulip/zulip/issues/6096 - Movim - nop - https://github.com/movim/movim/issues/63 ...
Re: Slack Is Buying HipChat from Atlassian
#564Earlier quoted context omitted.
Is it okay to rely solely on websockets these days? I was always impressed by pusher.com's commitment to a variety of fallback protocols (and there are three blog posts about it, see https://blog.pusher.com/how-we-built-pusher20-part-1/ )
> Is it okay to rely solely on websockets these days? Not affiliated with anyone here, but I think the answer is yes.
Re: Slack Is Buying HipChat from Atlassian
#565Earlier quoted context omitted.
Probably because they don't want to (or can't) have a huge portion of their company's internal communication stored forever on a third-party server. I still find it hard to believe that so many companies are okay with doing that.
And yet most large companies are using AWS and the like. This obsession with "MUST be behind OUR firewall!" is very arrogant, penny-wise pound-foolish thinking - and it tends to wither in the face of a frank, honest cost/benefit analysis. Amazon probably has more, if not better, security and engineers than most of the companies we're talking about.
And Slack has...? A bunch of VC money and a hastily thrown together chat app?
Re: Slack Is Buying HipChat from Atlassian
#566Taking out a competitor is good for Slack, said Butterfield: “There’s fewer choices for people.” What a statement! This is why I dislike Slack as a company and as much as I hate Teams (have to use it at work), I have no problem with it if the choice is Slack or Teams.
Re: Slack Is Buying HipChat from Atlassian
#567What bothers me the most with the current on-premises chat solutions is the lack of a true alternative for jabber/xmpp with OTR (or equivalent e2e encryption) support. I honestly hate that in 2018 there is no way to move away from Pidgin/Adium if you want to keep this functionality. - RocketChat - OTR breaks very easily, and https://github.com/RocketChat/Rocket.Chat/pull/10094 has been open for months - Matrix / Riot…
Re: Slack Is Buying HipChat from Atlassian
#568Earlier quoted context omitted.
The client-side story of XMPP is pretty bleak, especially if you're trying to get non-technical people to use it.
Already tried Movim :) https://movim.eu/ ? It's a fully-featured web-based XMPP client. It integrates all the modern XMPP features (message editing, history management, file-sharing, video-conferencing, publications…), it's responsive and easy to use and deploy on a self-hosted instance.
Over the past years I used 'Pidgin' as my desktop client, but it was not were I wanted it to be so I was actively looking for alternatives. Dino looked very promising on paper (supported XEPs) but they lack basic stuff like systray support (at least the last time I checked it out).
For a long time Gajim wasn't any better than Pidgin, but earlier this year they released their version 1.0 which added support for some more XEPs most importantly MAM (enables proper history synchronization between clients). Since that release I switched to Gajim and stopped looking for alternatives ;-)
Re: Slack Is Buying HipChat from Atlassian
#569"Taking out a competitor is good for Slack, said Butterfield: “There’s fewer choices for people.”"
I know most tech CEOs might think it, but you don't say it out loud!
Re: Slack Is Buying HipChat from Atlassian
#570Earlier quoted context omitted.
Enterprise E20 pricing (with the all-important high-availability clustering feature) is unlisted. Yeah, going back to opaque pricing and needing consultants to take care of anything and everything is a real step up /sarcasm
It's the only way to run a business. Everyone has different needs, different existing environments, different service expectations+++ So you can't effectively stick to one price for the "large" tier. Given the differences in complexity and capacity consultants are needed. Startups can't build in-house service teams - the economics are misaligned. Not that you can get away from consultants if you buy from Salesforce,…
Why not communicate using a made-up or real life anonymized case-study? Example: For people organization, with an environment of type , it typically costs per user. To be really effective give 2, 3 such example scenarios.
Potential customers would be more than happy to extrapolate from this data to start their internal discussions.