4 ms·
Slack was fine for our team of ~10, but frequently blocked by Chinese great firewall, and overall experience was slow. We moved to a free self-hosted Mattermost
by mstaoru 4y ago
Slack was fine for our team of ~10, but frequently blocked by Chinese great firewall, and overall experience was slow. We moved to a free self-hosted Mattermost instance and been using it for a better part of a year. Conversations are fast, we own our data, and there is no looming 10000 messages limit all the time. Bleve search is working just fine for us as well. Win!
Mattermost is an amazing product with a few quirks:
* it is hard to set up any kind of integration with a TUI: `matterircd` is quite buggy and also eats the CPU like there is no tomorrow, `matterbridge` doesn't sync correctly, or at least we couldn't make it work, and `matterhorn` is a standalone product (which would be much nicer as an e.g. weechat module) trying too hard to look like a web UI;
* web UI is still being polished, e.g. if you connection is unstable, web UI websocket is going to behave badly, requiring frequent refreshes to not miss any messages, or it still doesn't scroll to bottom sometimes on new messages, this has been the case since v.4.x and we're now on v.7;
* what I think is different from Slack is that threaded responses are shown in the main channel as well, and if there are many threads it is the same mess as if there were no threads at all :D
* somewhere around v.6 update the Focalboard push was a bit jarring, thankfully after disabling the plugin it disappeared for good.
Keep up the good work! Once our org is larger and requires Enterprise features, I'm pretty sure we stick with Mattermost.
- agnivade 4y ago> web UI websocket is going to behave badly, requiring frequent refreshes to not miss any messages, or it still doesn't scroll to bottom sometimes on new messages, this has been the case since v.4.x and we're now on v.7; That shouldn't be the case with 7.0. We recently released a feature called "reliable websockets" that makes a connection reliable across websocket disconnects. If you have any repro steps, please feel free to create an issue and we will take a look. > what I think is different from Slack is that threaded responses are shown in the main channel as well, and if there are many threads it is the same mess as if there were no threads at all :D With 7.0, our Collapsed Reply Threads feature is now in GA: https://mattermost.com/blog/collapsed-reply-threads-generally-available https://mattermost.com/blog/collapsed-reply-threads-generall.... Feel free to enable it to get a better threading experience.
- mstaoru 4y agoOh nice, we just upgraded to 7.0 this week, it was not a daily issue, so perhaps now it's gone. Will try the collapsed threads as well! Thanks a lot!