11–20 of 248 posts
The article talks about Hipchat as a competitor but HipChat was shut down by Atlassian and HipChat users were strongly encouraged to adopt Slack: https://www.atlassian.com/partnerships/slack
The article talks about Hipchat as a competitor but HipChat was shut down by Atlassian and HipChat users were strongly encouraged to adopt Slack: https://www.atlassian.com/partnerships/slack
Not entirely accurate. It's was bought by Slack, and then shut down.
I like that Mattermost is written in Go and can deploy on-prem with Docker. Those are two huge points for MM over Slack IMO.
For anyone looking to give it a try, here is a Dockerized version of Mattermost: https://github.com/mattermost/mattermost-docker Very straightforward and easy to set up.
Plus I have a simple traefik + compose setup so I can easily have it all automatically routed with a subdomain and https.
I might recommend something more robust for businesses in production but man is it easy. Want to try node-red? Done. Want to destroy - and it's gone, no need to futz around with dependencies.
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.
20+ years ago corporate IT was concerned about the phone on my desk (how quaint).
They put one there on the back of a PBX.
They put in a system that was LOCAL for local needs and accessed the public network when it needed to.
It worked because it was built on the back of a proven standard (telephone).
We don't have a working chat standard, and it shows and we need to fix it.
The article talks about Hipchat as a competitor but HipChat was shut down by Atlassian and HipChat users were strongly encouraged to adopt Slack: https://www.atlassian.com/partnerships/slack
The article talks about Hipchat as a competitor but HipChat was shut down by Atlassian and HipChat users were strongly encouraged to adopt Slack: https://www.atlassian.com/partnerships/slack
> HipChat was shut down by Atlassian Not entirely accurate. It's was bought by Slack, and then shut down.
This space is downright awful. 20+ years ago corporate IT was concerned about the phone on my desk (how quaint). They put one there on the back of a PBX. They put in a system that was LOCAL for local needs and accessed the public network when it needed to. It worked because it was built on the back of a proven standard (telephone). We don't have a working chat standard, and it shows and we need to fix it.
IRC works pretty well.
The only thing I sometimes miss is history, but... in some ways that's not a bad thing, and could be added without too much trouble.
Slack has history because Slack wants you to live in it. No history emphasizes that chat is ephemeral and something to tune in and out. Use email or something else for more permanent discussions.