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…
Story of Mattermost: Open-Sourced Competitor to Slack
181–190 of 248 posts
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#182Yeah. But. https://github.com/mattermost/mattermost-server/issues/6320 Non-admins can delete/archive any channel #6320
Thanks for highlighting this. It's a ticket from two years ago and this thread is a good opportunity to share more of the context and intention of how we think about Team Edition vs Enterprise Edition.
I've shared a reply on the ticket here: https://github.com/mattermost/mattermost-server/issues/6320#...
Also, I don't know if the ticket title is highly accurate--a non-admin can't delete any channel:
1) There is no "Delete Channel" in the UI only "Archive Channel"
2) A non-admin cannot archive any channel, only channels of which they are a member.
3) A non-admin archiving a channel they created is not really an issue, so this ticket is really about a "Non-admin can archive a channel which they are a member of but didn't create" which we've seen can be more helpful than harmful--when someone leaves a team and their out-of-date channels remains anyone can go and archive them without having to find an admin and make a request.
The current wording sounds like non-admins can delete private channels, channels on different teams, channels they're not part of, etc. and in my mind it's not the case. But perhaps other people have a different read?
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#183Used 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.
Opened a ticket here: https://github.com/mattermost/mattermost-server/issues/13422
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#184The 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…
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#185Love 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…
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#186The 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…
Thanks for the feedback, replies on both issues posted:
https://github.com/mattermost/mattermost-server/issues/6320
https://github.com/mattermost/mattermost-server/issues/5935
Please let us know what y'all think?
The password policy was added to Team Edition back in June, 2018.
>Mattermost isn’t any kind of a competitor to free-tier Slack
Mattermost isn't intended to compete with Slack's free tier.
The open source version of Mattermost is focused on software builders and operators who want a flexible, open, collaboration platform that works with their tools and workflows. Here's more on Mattermost Chatops as an example: https://mattermost.com/blog/introducing-mattermost-chatops/
Very often we're deployed in high security environments and private clouds where internet-based services can't easily go.
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#187I'm a programmer with experience in backend development and security and would be willing to donate some time to work on developing a stronger community implementation of Mattermost - only I'm not sure what the legally correct way is to go about it. What I'm hoping to find is a FOSS sherpa to help me navigate setting up a new project.
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#188We've been using Hipchat for years at $work. There's very little is say is "good" about it, it was just the best option at the time as it needed to be self-hosted. Mattermost is being trialled now, pasting code doesn't seem a lot better, but the overall experience is. As a place that likes Go/Docker it has potential for us.
What issues did you have with pasting code in it? It supports Markdown so it supports whatever a typical README.md would.
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#189We've been using Hipchat for years at $work. There's very little is say is "good" about it, it was just the best option at the time as it needed to be self-hosted. Mattermost is being trialled now, pasting code doesn't seem a lot better, but the overall experience is. As a place that likes Go/Docker it has potential for us.
The "$work" notation could be mistaken for the Slack stock ticker. The "$" is how you commonly denote stocks, and "WORK" is the ticker for Slack.
Re: Story of Mattermost: Open-Sourced Competitor to Slack
#190Uber currently uses Mattermost but will most likely move to Slack. During my 2 years at Amazon, the SFO based Prime Now team used Mattermost but we were eventually forced to move to Chime a pitiful example of a chat client.
Mattermost CEO here, if Amazon is open to it, I’d love to see if there is a “Better together” story across AWS, Chime (meetings, voice, video, screen sharing) and Mattermost (developer, Ops and SRE workflows and integrations). We’ve heard the same from different Amazon teams looking to accelerate developer productivity