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

571–580 of 730 posts

Re: Slack Is Buying HipChat from Atlassian

#571

Post by Arathorn »

arendtio wrote: post #560
Arathorn wrote: post #266

Earlier quoted context omitted.

Disclosure: i work on Matrix. We're basically doing nothing but fixing Synapse's performance problems currently, and improvements are on the horizon. We're late because we got sidetracked fixing flaws in the protocol, but as of the last few weeks we're back on perf again. So far we've sped up /sync by 2x and reduced CPU by about 20%, but the RAM improvements should land over the coming weeks unless we have further di…

Why is you current solution so ressource hungry? I mean, my 10-active-users off-the-shelf XMPP server (ejabberd) uses about 100MB RAM currently.

a 10 active user Synapse should use about 1GB max, so unsure what’s up with the earlier post. The reason it’s currently so much heavier than XMPP is that resource usage scales with the size of rooms being participated in, not the number of connected users - and we aggressively cache those rooms in RAM. However, 100MB is a much more sensible target and we’re busy optimising to try to shrink things down.

Re: Slack Is Buying HipChat from Atlassian

#572

Post by ge0rg »

drcursor wrote: post #563

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

OTR hasn't aged very well (it doesn't support asynchronous communication, multiple parties or multiple clients per party). For XMPP there is OMEMO, which is gaining traction (and is based on the Signal ratchet), but like with OTR, the forward secrecy it provides might be unwanted or even forbidden in corporate environments where you have retention policies in place. E2EE is great for private chats over an untrusted cloud provider, but really not a priority in enterprise environments.

Re: Slack Is Buying HipChat from Atlassian

#573

Post by jillesvangurp »

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…

On premise is apparently not big enough as a market for Atlassian. This does not surprise me: it needs a lot of hand holding; and saas gets you revenue much cheaper because you get economies of scale and much less support headaches. On top of that people get stuck on old versions of your product, which you then need to support as well because they payed you a premium for it. With SAAS you just have one version to worry about: the current one. So I don't expect Slack will be very eager to do on premise installations any time soon. The whole point of Slack is not doing that. In the same way, on site salesforce installations are not a thing, or on site Google docs. Even MS is moving away from on premise with office 365. Seat based, annual license revenue is a nice thing too for them.

Those who really want to do on premise, will find their way to one of several niche products in this space. But I don't think any of these players will grab a lot of market share. Ultimately anything run on site is going to be expensive to support and why bother when you get cloud based offerings. Compliance issues can be addressed in the cloud as well.

Re: Slack Is Buying HipChat from Atlassian

#574

Post by corv »

mnm1 wrote: post #540
corv wrote: post #518

Earlier quoted context omitted.

It’s also possible to mute chats, disable notifications and revisit them periodically. You get to decide if you want to communicate asynchronously.

I don't see how this helps when someone is demanding your attention in your personal life or at work. But it will definitely make things worse with people who demand exclusive attention and on the job possibly get you fired.

The clichéd answer on HN would be to change your employer if your working environment doesn't allow you to concentrate on the job.

As for devops alarms, those should be firing on multiple protocols and platforms anyhow.

Anything else can usually be better accomplished by announcing "office hours" during which you can be reached 1-on-1.

Re: Slack Is Buying HipChat from Atlassian

#575

Post by kennydude »

tabbott wrote: post #487
AntonyGarand wrote: post #479

Earlier quoted context omitted.

To be fair, there are tons of very low severity vulnerabilities disclosed on HackerOne and this does not mean the application is vulnerable. Slack is definetly not vulnerable because it is written in php and you can pollute an iframe on their career website. Having such a program in place is actually good for the application security as it does get audited by tons of hackers thanks to the monetary rewards.

I agree it's theoretically possible to write a secure project in PHP, but it's very difficult, especially if you're hiring people like crazy. If you divide the amount they've paid out in bounties by the number of bounties paid, and compare with their bounty tier rules, it's clear that a lot of the vulnerabilities that were reported in Slack are relatively severe. (And I agree bug bounty programs are great; we also us…

If you use a framework like Laravel it probably covers most things.

You could easily write a massively insecure application in core python, but things like Zulip use Django which shields you from most of it.

Re: Slack Is Buying HipChat from Atlassian

#576

Post by flipp3r »

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…

> Slack doesn't have an on-prem option.

Yes it does, the thing is you have to talk to them to get it and it costs about 10 times as much as on-prem HipChat.

The company I previously worked for switched to RocketChat for this reason (Slack asked ~100K vs HipChat ~10K). RocketChat is free but you'll have to manage it yourself.

Re: Slack Is Buying HipChat from Atlassian

#577

Post by _V_ »

it33 wrote: post #334
JeremyNT wrote: post #280

Earlier quoted context omitted.

I'll counter that anecdote with an observation that I have never observed any of those issues. In our deployment Mattermost is reliable and I've never heard any complaints like those from my colleagues. It could be a question of scale; we only have probably 50 or so regular users. That said, even though it works as advertised the product is not perfect. The Mattermost UI is bare bones and some things like conversatio…

Thanks @JeremyNT! Mattermost team here. May I ask which Mattermost version you're running? Also, what features would you like to see? We ship new improvements monthly, so if you're on an older release you could quickly add a lot of features: emoji reactions, GIF selector, custom emojis, Slack-compatible keyboard shortcuts, hashtags, slash comments, Slack-compatible integrations, etc.

I, for one, would like to see normal package upgrade process - atleast for debian-based distros.

I really don't like the current way of "copy old directory somewehere, copy a new one and replace some files from the old one". That is very painfull and this process does not really invoke a lot of confidence.

edit: typo

Re: Slack Is Buying HipChat from Atlassian

#578

Post by xPaw »

rspeer wrote: post #408
plett wrote: post #322

Earlier quoted context omitted.

thelounge is an web based IRC client with persistence like irccloud, except that thelounge is open source and self-hosted. https://thelounge.chat/

A web-based client is not going to provide adequate persistence on a smartphone.

Lounge works fine on a smartphone because the actual IRC connection would be handled by a server where you host it, not your own phone.

Re: Slack Is Buying HipChat from Atlassian

#579

Post by krzyk »

strictnein wrote: post #128
bitwize wrote: post #113

Earlier quoted context omitted.

Hey, it could be worse. It could be VersionOne.

VersionOne has the advantage of being too clunky for middle managers to figure out.

V1 is too clunky to figure out by developers (or any human being for that matter) and looks like something designed in the 90-ties.

Re: Slack Is Buying HipChat from Atlassian

#580

Post by nyconyco »

Hey 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 to fix all that with Nayego: https://nayego.net/ Nayego is an open source team chat under development, that has a world-class UX, and that is federated/decentralised/federated like email.

Nayego wishes to address the organisations that are open and extended, where teams are working together with other internal teams, and with partners, customers, providers, but also freelancers, and remote and home office workers.

Nayego is and will remain free/open source and open standard (XMPP, SIP, WebRTC). If you wish to register to the preview, please go to: https://nayego.net/ We will do our best.

Post reply on HN