Synapse VS Mattermost

Now, the Matrix Foundation has decided to use Rust to improve bits and pieces of their Gen 1 Home Server - Synapse. The server itself is still largely in Python though. That being said, some of the improvements to the performance of Synapse based home servers can partly be attributed to the usage of Rust.

Here: https://github.com/matrix-org/synapse/blob/develop/docs/workers.md

Matrix Server

For synapse it's not possible (https://github.com/matrix-org/synapse/issues/7076). I don't know about the other server implementations

Issue "README claims you can run a "hot spare" synapse, which is incorrect #7076" points to "multi-master setups" in issue Shard master process. #6677 which continues in issue Shard master process. #7593.

Synapse has a docker image...https://github.com/matrix-org/synapse/tree/develop/docker

• Matrix (synapse) for LibreNMS

One of the main methods for adding redundancy to Synapse Matrix is workers, which you can read into here. On top of that, with simple scripting you can set two servers to run the same master Synapse, such that when one goes down, the other spins up, so that updates and such have extremely low downtime. I'm vaguely aware of there being more you can do being those steps as well but I haven't looked further into it.

Initially I started with Matrix-Synapse. The toughest part was figuring out how to setup a subdomain to host my matrix server on, while still being able to point users to the main domain when they sign-up. (@user:example.com instead of @user:matrix.example.com). Once I figured out how delegation worked with a reverse proxy I got it working and figured id try dendrite. Dendrite is the second generation matrix server written in Go and it I think its configuration is easier and its footprint is smaller than matrix-synapse. However since its still a work in progress and its in beta stages some features aren't implemented and there were a few hiccups that made me switch back to matrix-synapse. So when dendrite is good to go I'll definitely be switching to that.

The agents can now send notifications to Mattermost, using the Slack integration! Mattermost has a Slack-compatible API that only required a couple of additional parameters. Kudos to @je2555!

Our military uses this program to communicate classified information and it's open-source. "Everyone can see the code therefore it is easier to circumvent" is false logic. https://mattermost.com/

More leaning to the Slack side, but Mattermost could be an option for you.

Mattermost

Mattermost can be self-hosted and actually comes with GitLab Omnibus deployments iirc (albeit disabled by default).

Depends on how you're using Discord, but there's Mumble, Mattermost, and Element/Matrix

On the server platform side, we continue working on improvements in mmctl regarding import and export (better error messages, better user experience). We also are close to wrapping up proper rollback support for our database migrations.

I too have been frustrated by the lack of kanban projects with mobile. I personally prefer a native mobile app vs a webpage. What I ended up settling on was Mattermost . I think it should tick most of your boxes.