Synapse VS dendrite

Synapse

The permanence is a difficult issue, there are some description here and here, and some proposed solutions here and here , but the main point is that in a federated system you can not be sure about that the others will work in a good faith. If you have shared or sent something to someone outside the infrastructure you control, you can not reverse that. Like if you have sent an email from protonmail to a gmail address, you can not force google to delete that.

Discord? There are many options, but Mattermost is probably the most Discord like. You might choose Matrix instead if you want something federated like the other platforms I've linked here.

Meh.

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

I really hope that Dendrite is getting more traction and maybe there's an OIDC solution for Matrix one day.

This is what the Matrix team is developing Dendrite for. To have a feature-complete yet small server software. But it's still in beta.

Pinecone, which is an experimental overlay routing protocol used by P2P Matrix. It and Dendrite are extremely important to P2P Matrix.

Dendrite, meanwhile, can be found here. They say it's in beta. I think it's a late Alpha. Dendrite's primary mode is "Monolith"; this will have many of the same scalability/balancing options that Synapse does. However the true benefit to Dendrite as I see it is the "polylith" mode where workers can swap around which worker is the master without any interruption of service. I do not think that Dendrite polylith works yet, but I might be wrong. I'll be looking at running it on a test server in January to see if it's time to upgrade from Synapse (and time to invest in 4-6 SBCs to keep three here and send 3 to 3 of my buddies to make my Matrix even more reliable).

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.

You could also try dendrite, it's also an official server implementing the matrix protocol but it's way lighter and seem easier to setup. It's still not a full replacement of synapse because it lack some features but for a private usage it should be more than enough

Somebody made good experience with https://github.com/matrix-org/dendrite?