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

Story of Mattermost: Open-Sourced Competitor to Slack

breakoutstartups.substack.com

Post reply on HN
Print view View original

231–240 of 248 posts

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

#231

Post by the_icelander »

maxpert wrote: post #162

Love the fact people are adopting Opensource solutions but corporates won’t budge. I think the hardest penetration for anyone right now is Microsoft Teams. Since they started bundling teams with Office they have been able to boast about numbers and actually hurt Slack. I wonder what is roadmap for Mattermost. Shameless plug I myself did an opensource version of a chat server called raspchat https://github.com/maxpert…

My response to someone insisting on using only Microsoft Teams is: What if Teams goes down? How is the IT team going to coordinate bringing it back up? Email? SMS?

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

#232

Post by the_icelander »

Andrew_nenakhov wrote: post #58
secfirstmd wrote: post #44

I'm a big Mattermost fan but it really needs end to ends encryption. Also the Android mobile app is pretty weak.

Standard tls between server and client helps against any outside threat. The only threat from which e2ee helps better than tls comes from the server admin. Now, do you REALLY need end to end encryption to protect yourself from a person running your team chat server?

Not for business, but if you want to get your friends on a chat server it would be easier if they knew you couldn't see everything they said.

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

#233

Post by slig »

kevindong wrote: post #165
slig wrote: post #66

Earlier quoted context omitted.

For $20/m ($5 for a droplet and $15 for a managed DB instance) you can have that peace of mind on DO.

There's much more to hosting a service than standing it up on the modern equivalent of an VM and assuming it'll never need to be touched again.

Sure, but the parent was talking about the difficulties of handling a DB server.

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

#234

Post by slig »

sjy wrote: post #149
slig wrote: post #66

Earlier quoted context omitted.

For $20/m ($5 for a droplet and $15 for a managed DB instance) you can have that peace of mind on DO.

Paying $15/month for a managed database is not self-hosting.

One would still have the fun of maintaining the application server updated.

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

#235

Post by gerbilly »

it33 wrote: post #227
gerbilly wrote: post #222

Earlier quoted context omitted.

I can't really tell for the github issues you posted what was done about these two issues. I don't really feel like reading all that just to figure it out. Did you resolve both of the issues brought up by OP or not? (Answering: "The password policy was added to Team Edition back in June, 2018.", isn't the same as answering, "the free tier allows passwords of length >5 characters.")

Sorry about that. Thanks for the feedback. It is very helpful. Trying again: 1) Enforcing password requirements for end users was put in free tier last year - Here's why, with a link on how to use it: https://github.com/mattermost/mattermost-server/issues/5935#... 2) Non-admins are still able to archive channels they belong to but did not create - Here's why: https://github.com/mattermost/mattermost-server/issues/632…

Sure, thanks! I'm not panning you or your product.

I'd love for there to be a viable alternative to slack that is more (if not entirely) open.

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

#236

Post by Operyl »

sneak wrote: post #205
Operyl wrote: post #172

Earlier quoted context omitted.

I believe they store the enterprise specific code in another git repo that has to be checked out, for one (from reading their Makefile).

The binaries they release (including that code) are MIT licensed according to their readme, which means that modifying those should also be no problem.

This is true, you could probably edit out the publickey and then generate your own license pretty easily.

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

#237

Post by ergothus »

e12e wrote: post #113
mrmuagi wrote: post #89

Earlier quoted context omitted.

> Email has hefty overhead per message. I don't think that poster was talking about protocol innards, although kudos for you for having that knowledge, but perhaps they were, but in terms of user experience, slack/group chat is very low cost in terms of requiring any sort of mental pause before sending the message, specifically as a cost for the message itself. So much so, that a type of usage of verbal diarrhea can…

Interesting points. I suspect this is why chat is such a crap, low-throughput form communication; it's trivial for the sender to ship of a half-assed message - and very hard for the receiver to handle low-hundred conversations in a work-day - precisely because few(er) senders take the time to write a short, but dense message - and expect a reply-response dialogue "to quickly sort things out". Which is much harder to…

> I suspect this is why chat is such a crap, low-throughput form communication; it's trivial for the sender to ship of a half-assed message

I think the crap is related to the amount of effort put into the message vs the medium. Making it easier/harder to send a message MIGHT change the quality, but I'd argue the decay of email over time was due to people failing to put in any effort DESPITE the minimum required.

I recall a coworker back in the late 90s talking about their usenet program, that made them click through a "Warning: What you are about to send will be read by thousands of people. Are you sure you want to send it?" message (paraphrased from memory). He found it daunting and therefore bad, I thought it was properly daunting.

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

#238

Post by 1000units »

gyrgtyn wrote: post #160
SquishyPanda23 wrote: post #138

Earlier quoted context omitted.

What you're describing sounds similar to crippleware. https://en.m.wikipedia.org/wiki/Crippleware

not sure that's pc buddy

I am sure that it's a fine piece of language to use, particularly in this context.

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

#239

Post by pietroglyph »

pc86 wrote: post #220
antioedipus wrote: post #137

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.

Now that I read my comment again, it is clear that I was being more inflammatory than was necessary.

Thank you for calling me on it.

(As an aside, this is one of my highest upvoted comments ever, which perhaps says something about what gets internet points on HN.)

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

#240

Post by jjeaff »

it33 wrote: post #191
jjeaff wrote: 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…

Mattermost CEO here, Fantastic! Thanks for sharing back--comments like this are super motivating for everyone working on the project,

Good to hear!

I'll add that the only issues I came across were from a few users who didn't like the mobile client as well as Slack. I would chalk most of that up to them simply being used to Slack.

But I think Mattermost could still use a little bit more polish (as pretty much all software could) when it comes to the clients. I hope you guys don't lose focus on that. I would much rather have a progressively better user experience than one more widget integration that most won't use anyway.

Post reply on HN