Live data from Hacker News

Story of Mattermost: Open-Sourced Competitor to Slack

breakoutstartups.substack.com

211–220 of 248 posts

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

#211

Could anyone elaborate as to how Microsoft Teams overtook Slack so quickly?

> Could anyone elaborate as to how Microsoft Teams overtook Slack so quickly?

easy. they didn't:

https://twitter.com/msquinn/status/1179874609899827200

https://venturebeat.com/2019/11/21/microsoft-teams-giddy-gro...

MSFT decided that one clear way to increase their share price is for their new product to run at all times for everyone.

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

#212
post #184

The open-source Mattermost intentionally lacks a couple of pieces of basic functionality to push you to pay, like the ability to stop regular users from deleting channels, and no way to set a reasonable password policy that requires more than 5 characters. Mattermost (and specifically their CEO, who is vigorously replying to messages on this thread, but probably won’t engage with this one) haven’t responded positivel…

Another one, if you want your free local instalation to be able to push notifications to your mobile app it needs to go through their http (non-https) proxy. At this point this might be more damaging than not providing the option at all.

You can set it to push only that a message was sent, redacting the user/channel and content.

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

#213
post #174

Used Mattermost for a year, and I can attest to it's shittiness. There is a bug during switching channels that pins your view to some random location weeks before the latest post. The result is that switching channel in Mattermost has a 60% chance of requiring you to spend the next 30 seconds scrolling the window to the bottommost-recent-message. Horrible.

That's no good, but wouldn't hitting/holding your `End` key be faster?

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

#214
post #179
post #103

Earlier quoted context omitted.

> Let's remind that Open Source fundamentally means _no expectations_. No. Open Source, as defined, is about what the end user is allowed to do with the code they have. That’s it. What you describe is common , but not inherent. There are plenty of exceptions, like if you get Red Hat, you’ll get to have plenty of expectations, and Red Hat is still Open Source . Please stop the ancient FUD about Open Source means havin…

When I say open source means no expectations of support I obviously talk about the license the software comes with, not the overall idea and goals that are common in the open source world. You want support! Great, it exists and can even provided by multiple different actors, with or without expected quality of service, and that's great! But that is not included in the license, you have to find another arrangement on…

> But that is not included in the license

No license includes anything like that. That’s not what a software license is.

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

#215
My Fortune 500 healthcare company successfully uses Mattermost because the lawyers aren't comfortable with us using slack. It's been great. Thank you @it33 and team.

p.s. we haven't run into the issue 6320 (users archiving channels), for exactly the reasons @it33 described in the issue report. He didn't explain it well, but permissions is a complex rathole, un-archive is a simple workflow for admins and if there's continued abuse, just ban the user.

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

#216
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…

I had similar needs. I don't like that telemetry is on by default and you can only disable it by manually editing the config JSON (whilst service's stopped). I have encountered bugs in past versions but nothing recent stands out. Having full control of our data, unlimited history, slack-compatible integrations with 3rd party notification services and our own, easy upgrades, and no downtime when Internet's out (in-office server) has been great. Overall a positive experience.

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

#217
post #45

We went Skype => Slack => MS Teams => Mattermost for our developers. If Teams wasn't such garbage at basic things like markup and pasting screenshots, we might still be using it for everything. I had no real concerns with Slack from a development perspective. We simply wanted to try a unified messaging platform for the whole enterprise (our non-developers much prefer Teams/Skype for some reason). That experiment fail…

What's the reasoning behind no updates?

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

#218

For a while we used Mattermost at my office. At the time we had a handful of startups in our incubator. Eventually we ended up switching to Slack. I don't think it had to do with anything other than momentum and popularity of Slack, in spite of Mattermost accomplishing the same thing with virtually the same interface, people just liked and wanted to be on Slack...

Slack is using cloud/external storage. Many companies have policies against that,making MM is surprisingly popular in banks and such. Personally, can't tell the difference between two

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

#219

The open-source Mattermost intentionally lacks a couple of pieces of basic functionality to push you to pay, like the ability to stop regular users from deleting channels, and no way to set a reasonable password policy that requires more than 5 characters. Mattermost (and specifically their CEO, who is vigorously replying to messages on this thread, but probably won’t engage with this one) haven’t responded positivel…

This is, fundamentally, the Open Core business plan, which Mattermost is executing quite successfully. You get all the marketing benefits of being "open source", but few IT departments will use your software in production without buying the enterprise license, so you get most of the revenue you'd have had if you were closed source. Folks have different perspectives on Open Core. It's definitely a lot better from a fr…

I really hope this model works out for you, I absolutely adore Zulip. At my company, we have the option of self-hosting, since you've made it so easy, but I intentionally keep us on the free plan so we can start paying when we can afford it, to support you.

Zulip is one of the few pieces of software that I think are unquestionably worth their price (some others being Gitlab and some sort of SIP provider, e.g. OnSIP).

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

#220

The open-source Mattermost intentionally lacks a couple of pieces of basic functionality to push you to pay, like the ability to stop regular users from deleting channels, and no way to set a reasonable password policy that requires more than 5 characters. Mattermost (and specifically their CEO, who is vigorously replying to messages on this thread, but probably won’t engage with this one) haven’t responded positivel…

> Mattermost (and specifically their CEO, who is vigorously replying to messages on this thread, but probably won’t engage with this one) [emphasis mine]

Aside from being wrong, this seems needlessly argumentative and rude.

Post reply on HN