Earlier quoted context omitted.
I think the fact that you must give a thread topic to send a message. It's not particularly difficult concept, but different from every other chat app. And for a large user base being confronted with this demand "when they just want to send a message" is frustrating.
Zoho Cliq solves this by using ML to parse the message and give a suitable name. It's suitable 7/10 times, and the remaining 3 - it either doesn't matter that much or is trivial to rename. Zulip should try that if they haven't already.
Mattermost – open-source platform for secure collaboration
81–90 of 128 posts
Re: Mattermost – open-source platform for secure collaboration
#82It's good that this exists, but Mattermost's threads are very suboptimal. If Alice posts a message and Bob replies, then _that is_ the thread. If that thread goes into a certain path you can't branch off of it, you can't reply to Alice's original message if you're talking about a different thing. I don't know if this makes sense, but hopefully you got my point.
You can't also move messages into a thread as admin. Which is a bit annoying.
[0] https://github.com/gabrieljackson/mattermost-plugin-wrangler...
Re: Mattermost – open-source platform for secure collaboration
#83Almost four years ago someone raised the issue of multiple mattermost servers in the mobile applications ( https://mattermost.atlassian.net/browse/MM-11067 ). Two years ago someone on the mattermost team promised the new mobile application would be there by the end of 2021. Yet in June 2022... you get the gist. Not a fan.
Thanks for your feedback! Mattermost PM here, We now have multiple Mattermost server support in the mobile apps in Beta! If you're interested to try it out, here's how you can join the Mattermost Mobile app beta program. The community feedback on the Beta version has thus far being excellent, and helps us improve the user experience before we ship multi-server support as a stable release to everyone :) [1] https://ma…
One piece of feedback for you and your org: the whole mobile v2 process was not very transparent from the outside. I tracked the ticket from time to time but gave up after a year as no visible progress was being made. Maybe that happened in some Atlassian forum, which to be blunt I’m not going to create an account for simply to read a thread.
Re: Mattermost – open-source platform for secure collaboration
#84Earlier quoted context omitted.
What do you like about Mattermost that’s missing in MS Teams?
Teams is widely hated by many here because of its spyware capabilities.
Re: Mattermost – open-source platform for secure collaboration
#85I've run a Mattermost installation off the cheapest Digital Ocean droplet for about 4 years. Moved away from Slack due to the 10k message limit and the fact that I could self-host it. Unfortunately, while it does keep your history, the search is pretty lousy (there is a better search available for paying customers) and you can't export private conversations (unless you pay them). They gotta make money, and I'm not pa…
In enterprise editions, the only addition is Elasticsearch. But in our open-source version, we do have support for https://github.com/blevesearch/bleve. Although, it's in beta, we have a lot of customers using it.
I am wondering if you have tried using it and didn't like it?
Re: Mattermost – open-source platform for secure collaboration
#86Mattermost is nice in that communication and project management is all in one tool, but doing anything within Mattermost is very sluggish (even on a very overspecced server with only 1 Mattermost user online). Using their Focalboard plugin resulted in multiple seconds of wait time between various actions like modifying a task. On the other hand, Zulip has been consistently snappy even as we've onboarded users onto our instance. Seeing it in use at large organizations such as Rust's Zulip instance instilled confidence that it'll continue to perform well even well beyond our scale.
Also Zulip's threading model is really nice to use once you and your team gets the hang of topic separation. We've managed to completely eliminate 'talking over one another' as we would in Slack/Discord style text channels, and it's much easier to keep track of various conversations. While Zulip's UI and UX isn't as polished and certainly has areas for improvement, the threading model alone makes it worthwhile to use.
On top of that, Mattermost's pricing doesn't work well for small businesses, especially when you factor in that something 'simple' like Elasticsearch support, or, performance monitoring tools to figure out why your 1 user installation on a 88 thread server with hundreds of GBs of memory is sluggish, or even just creating a second admin user is locked behind their enterprise plan.
I get that money needs to be made, but blocking some features behind an enterprise plan (that asks you to contact them for pricing, no less - their $10/user for the Professional plan is not only steep, but still doesn't include these features) doesn't feel great. Zulip is completely free, and offers Zulip Cloud alongside a support plan, but does not block any features behind a paywall. There's no limitations on what Zulip will let you do either - no 10,000 message history limit, no file storage limit, user role restrictions, or anything of that nature.
Oh, and Zulip is 100% open source software. In my eyes, it's hard to compete with that when it comes to communication tools.
Re: Mattermost – open-source platform for secure collaboration
#87They decided to up their price per user by a significant amount not too long ago... our self-hosted instance suddenly became more expensive than Slack but with an obviously not nearly as polished product as Slack. So we moved over to Zulip because at least they do their own thing, we haven't had any regrets over the switch to Zulip.
Re: Mattermost – open-source platform for secure collaboration
#88Earlier quoted context omitted.
Thanks for your feedback! Mattermost PM here, We now have multiple Mattermost server support in the mobile apps in Beta! If you're interested to try it out, here's how you can join the Mattermost Mobile app beta program. The community feedback on the Beta version has thus far being excellent, and helps us improve the user experience before we ship multi-server support as a stable release to everyone :) [1] https://ma…
Thank you for the feedback but I’m going to wait until it’s published in the respective App Stores. One piece of feedback for you and your org: the whole mobile v2 process was not very transparent from the outside. I tracked the ticket from time to time but gave up after a year as no visible progress was being made. Maybe that happened in some Atlassian forum, which to be blunt I’m not going to create an account for…
Out of curiosity, where would you have looked for such updates? GitHub issues?
Re: Mattermost – open-source platform for secure collaboration
#89Re: Mattermost – open-source platform for secure collaboration
#90Almost four years ago someone raised the issue of multiple mattermost servers in the mobile applications ( https://mattermost.atlassian.net/browse/MM-11067 ). Two years ago someone on the mattermost team promised the new mobile application would be there by the end of 2021. Yet in June 2022... you get the gist. Not a fan.
Thanks for your feedback! Mattermost PM here, We now have multiple Mattermost server support in the mobile apps in Beta! If you're interested to try it out, here's how you can join the Mattermost Mobile app beta program. The community feedback on the Beta version has thus far being excellent, and helps us improve the user experience before we ship multi-server support as a stable release to everyone :) [1] https://ma…
This is fantastic news!
It is/was a problem having to choose which server to connect to, when I had multiple Mattermost servers.
This new feature will fix that quandary
Different Question: can I point `mmctl` to your managed cloud instance (are the "free tiers" exempt from this ability but paid tiers allow this?), have it create a backup and restore that backup to a local Mattermost team (the OSS) instance? This is just to be able to migrate old team chats off the Mattermost cloud instance but retain the ability to quickly read them now and then if needed