Als Antwort auf Adrianna Tan

We use mattermost at our co-op and we applied the limitless.patch to get through the 10k message limit they impose on the free version.

framagit.org/framasoft/framate…

Als Antwort auf Adrianna Tan

I'm just a user, not on the admin side of things.

Work has a self-hosted RocketChat system that is quite usable as an alternative to Slack. There are some paid-only features like a cap on mobile notifications.

Element/Matrix works nicely for a hobby project that I'm involved in. I hear some people (generally) don't like it, mostly around cross-server compatibility issues, and I'm not sure it's as much of a replacement for Slack.

Dieser Beitrag wurde bearbeitet. (1 Woche her)
Als Antwort auf Adrianna Tan

Element and Matrix are essentially using the same thing. It's nice that one can have E2EE channels, but the UX is far from good. Different clients support different subsets of features, i.e. Element Classic supports threads, Element X and Fluffychat don't, and each has different bugs. Element Classic has more issues on iOS, where it sometimes loses the post that was quoted and displays null in its place. (1/2)
Als Antwort auf mlen

I would not use mattermost, they began enshittifying the project, so they can't be trusted not to do more things like this: github.com/mattermost/mattermo…

I never used Zulip, so I don't have an opinion on it. If I had to setup something similar, I'd try it. (2/2)

Als Antwort auf Adrianna Tan

The thing about Matrix/Element is that it's some kind of distributed eventually consistent graph database consensus algorithm with a chat app implemented on top of it as a proof of concept. So there's always some jank and more if you use the federation. It's more reliable if you host it and use it only internally but that's a lot of work. I wouldn't really recommend it.