Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack Is Buying HipChat from Atlassian

bloomberg.com

Post reply on HN
Print view View original

631–640 of 730 posts

Re: Slack Is Buying HipChat from Atlassian

#631

Post by ishaanbahal »

evrydayhustling wrote: post #475
ironjunkie wrote: post #165

When 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…

> Everytime I have a serious conversation about the productivity gains or losses of Slack though, it is pretty clear to me that it is more disruptive than helpful. So, the tens of thousands of teams paying for Slack either aren't having serious conversations or have decided the opposite. Here are some things I think you are undervaluing about team chat: - It replaces many meetings and phone calls that are more interr…

I'd say you should give Flock a shot! It does provide a very similar feature set and does some things differently! The ease you talk about is all there, a lot of third party app integrations are also there. The platform lets you run proper apps inside of flock, apart from the usual slash commands and bots. All the pricing grids provide video conference by default, even the free plan! And the pricing is way cheaper than Slack.

I'm a dev at Flock, and an ex-user of Slack in my previous company, I hardly miss anything Slack had that isn't there on Flock!

Re: Slack Is Buying HipChat from Atlassian

#632

Post by ezoe »

solatic wrote: post #107

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…

The company who insist the on-premises relies on proprietary software? What are they thinking?

Re: Slack Is Buying HipChat from Atlassian

#633

Post by SomeHacker44 »

it33 wrote: post #509
solatic wrote: post #107

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

We did this at my company; we already had self hosted free GitLab. We tied it into our AD and went happily without Hipchat about a year ago. Some things are rougher (image support) but it was mostly smooth and equivalent, and actually nicer in that it supported Markdown.

Recommended. And, a lot cheaper than Slack which is insanely expensive ($72/user/year) - of course it is not free as it takes up AWS server resources and DevOps time, but we control all our data and security now.

Re: Slack Is Buying HipChat from Atlassian

#634

Post by ninad »

ironjunkie wrote: post #165

When 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…

I feel a huge part of the value of tools like slack, MS Teams, flock, comes from not being cool chat tools but for bringing context into conversation and giving life to information. I've thought deeply about this over the past few years, and I feel it does add value.

I agree with capkutay, these are not problems of a tool, just like you can't help a coworker coming over to you and interrupting your flow, same applies here. I feel we will see more chat etiquette in enterprise and guidelines which will help avoid the tradeoffs. in my experience, the benefits outweigh the tradeoffs.

Disclaimer: I'm helping build flock.com

Re: Slack Is Buying HipChat from Atlassian

#635

Post by [deleted] »

it33 wrote: post #509
solatic wrote: post #107

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

[deleted]

Re: Slack Is Buying HipChat from Atlassian

#636

Post by lyqwyd »

it33 wrote: post #509
solatic wrote: post #107

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

I recently installed Mattermost open source, but will likely move to something else. This is a trial for me, but the lack of google authentication in the free version, and particularly that it is only available on the enterprise version with opaque pricing, which will likely be unaffordable for me at this point, is pretty much a deal breaker.

I understand you need to have different features for the different packages, but I think this is a feature that should be available for smaller businesses. The g suite is affordable for small businesses and startups, and I doubt it is particularly difficult to implement, so I suggest including it at a lower price point.

For me it’s not even worth continuing the trial without it.

Re: Slack Is Buying HipChat from Atlassian

#637

Post by rauhl »

it33 wrote: post #509
solatic wrote: post #107

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

I’ll add my own voice: I’ve been pretty happy with Mattermost (for both business & personal uses). It’s a bit tricky to set up initially, but once it’s set up it Just Works™ — and that’s the most important thing for a piece of software in my opinion.

It seems to get better every few months, which is nice. Doesn’t feel like it’s sitting on its laurels.

Re: Slack Is Buying HipChat from Atlassian

#638

Post by qaq »

BjoernKW wrote: post #622
qaq wrote: post #621

Earlier quoted context omitted.

They also become much more attractive targets for APT since compromising say Slack is way more interesting than some avg. mid size shop.

It depends on what an attacker is after. For the average mid-sized shop that's probably true. However, it's usually larger organizations that worry about storing data in the cloud. For these organizations and attacks specifically targeted at one of them, I suppose that in order to access vital company data both social engineering and hacking an internal system are much more effective attack vectors than gaining acces…

Depends if APT is say FSB or MSS Slack is very attractive target. But in general you are prob. right.

Re: Slack Is Buying HipChat from Atlassian

#639

Post by hellojason »

nyconyco wrote: post #597
LiquidFlux wrote: post #584

Earlier quoted context omitted.

Echoing Promarged, the world class UX claim had me searching for screenshots, not having any was a major turn-off.

I understand. A complete and comprehensive UX is not seen in a few screenshots...

You have several potential customers here telling you what they expect to see on a landing page when considering your product. If you’re this stubborn about listening to non-customers who are telling you exactly how to get them into your sales funnel, it gives the impression you would care less about their needs and suggestions regarding the product itself once they become customers.

Listen to your ideal customers, then regurgitate it back to them. If screenshots are not enough, how about a video? Discuss the pain points you’re solving, and show how you solve them. Maybe embed a chat session on the page and let me chat with a bot to feel why it’s better, but do something so I take your product seriously.

Re: Slack Is Buying HipChat from Atlassian

#640

Post by eadmund »

gregmac wrote: post #239
philwelch wrote: post #200

Earlier 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…

> 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).

I wonder how much of this attitude is a result of poor email client UIs. I switched over to using notmuch for my mail about a year ago, and I now consider email to be a great place for discussions: I can search my entire history almost instantaneously, far faster than with Gmail or Inbox.

> The problem I think most people run into with the realtime discussion is failing to document the outcome of the meeting -- and that of course goes into a ticket or long-term docs. A meeting with no notes or outcome might as well have not happened.

I definitely agree here. This falls under the heading of 'things we used to know as a society that we've forgotten.' Every meeting should have an agenda, even it's just a single agendum 'discuss $FOO,' and every meeting should have some sort of minutes, even if they're just 'discussed $FOO, decided to pursue course $BAR.'

Post reply on HN