Live data from Hacker News

Story of Mattermost: Open-Sourced Competitor to Slack

breakoutstartups.substack.com

31–40 of 248 posts

Re: Story of Mattermost: Open-Sourced Competitor to Slack

#33
post #9

What about zulip? They seem to fare well in terms of features against slack and mattermost.

I love Zulip but the concept of topics is repelant for (lazy?) users. When you chat on a channel (Slack, Mattermost) and people start fragmenting the discussion into several topics that interlace... Ugh! I yet have to meet people that would at last utilize Threads.

> When you chat on a channel (Slack, Mattermost) and people start fragmenting the discussion into several topics that interlace... Ugh! I yet have to meet people that would at last utilize Threads.

Slack threads are an utter abomination. I'd rather they removed the feature entirely; they're harder to keep track of than the linear stream of a channel (which is saying something, because the chronological, linear stream is already pretty bad for ongoing discussions)

Re: Story of Mattermost: Open-Sourced Competitor to Slack

#34
post #14

I have a small team, but about a year ago, we deployed Mattermost on our K8s cluster using their Helm chart and I have been very pleased with the performance and stability. We never looked back at slack. I have not had to fiddle with the configuration at all since deploying it. It just works. And that is also considering that to save costs, I launched it on preemptible instances which go down usually once every 24 ho…

Did you do any integrations for voice chat?

Re: Story of Mattermost: Open-Sourced Competitor to Slack

#36

Yeah. But. https://github.com/mattermost/mattermost-server/issues/6320 Non-admins can delete/archive any channel #6320

What's more disturbing than the bug itself is the Mattermost team's response that this behavior is intentional for the free "team edition" of their software, and that "actually, I think the bug is that we should not be showing Channel Admin as a role in Team Edition" (i.e, users of the free edition don't get any kind of access controls, making it impractical to use outside a small group of trusted users).

Potentially controversial opinion: This isn't really open source. When major features like permissions and access controls are stripped from the "community" version of a software package, it starts looking more like a feature-limited demo.

Re: Story of Mattermost: Open-Sourced Competitor to Slack

#37
post #32

I been a mattermost user for two years, can't say enough good things about it. Love that it's written in go. We run ours with very little resources and it still chugs along.

Why does it matter what it’s written in?

Go will often be faster than NodeJS. It can also be deployed as a binary rather than a blob of Node modules.

Re: Story of Mattermost: Open-Sourced Competitor to Slack

#39

Earlier quoted context omitted.

> HipChat was shut down by Atlassian Not entirely accurate. It's was bought by Slack, and then shut down.

Didn't they just buy the userbase? I don't think they bought the technology - they also made a lot of devs redundant after the purchase?

They bought the IP, not the product.

Re: Story of Mattermost: Open-Sourced Competitor to Slack

#40

Does Mattermost still have LDAP issues? The company I work for was looking for a Slack alternative but in the end decided to stick with Slack because of this.

What do you mean by LDAP issues? You don't get ldap with a free license, but there are still ways to get ldap auth despite that. (For instance, https://medium.com/p/mattermost-teams-edition-replacing-gitl...)
Post reply on HN