Synapse VS conduit

Compare Synapse vs conduit and see what are their differences.

Synapse

Synapse: Matrix homeserver written in Python/Twisted. (by matrix-org)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern API for authentication & user identity.
  • Onboard AI - ChatGPT with full context of any GitHub repo.
Synapse conduit
366 18
11,720 -
- -
9.8 -
2 months ago -
Python
Apache License 2.0 -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Synapse

Posts with mentions or reviews of Synapse. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-19.

conduit

Posts with mentions or reviews of conduit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-13.
  • Matrix 2.0: How we’re making Matrix go voom
    28 projects | news.ycombinator.com | 13 Feb 2023
    > "At least as standard" how?

    There are 8 people who vote on changes to the Matrix spec (the Spec Core Team), 7 of which are Element employees (including Matthew, Element's CEO). Element also controls the development of clients and servers used by the large majority of users in the public federation.

    > A substantial portion of the IRC comunity is actively hostile to the IRCv3 extensions, and in some cases prefer incompatible implementations of the same functionality; Matrix has nothing like that going on.

    But any IRC client will work fine on any IRC server, and they can connect to various servers with different implementations.

    On Matrix, clients (generally) can only connect to one homeserver at a time; which forces them to converge on following exactly the same spec. And if your server differs ever so slightly from the other ones in how it implements some parts of the spec (room consensus), then it can be split-brained from the rest of the federation. Instead, changes to the room consensus are done by pushing new room versions, and each server implementation needs to explicitly support it or they can't join it. This means Synapse devs (which are a majority of Element employees) get to decide what room versions can get traction.

    It is not uncommon for people in the Matrix community to complain about this and Element keeping specs in limbo, and PRs to the flagship clients being stuck in "design review tar".

    > And there seem to be more visibly independent implementations of Matrix than IRCv3.

    Clients, maybe, at least in the number of implementation. It's hard to find stats of this, but I feel that >95% of people in the public federation use Element even in tech-y rooms; IRC has a healthier mix of major clients (weechat, irssi, IRCCloud, Hexchat, KiwiIRC, The Lounge each have >5% of desktop/web users). But I admit that's just my very subjective point of view.

    In terms of servers, Matrix has three open source ones as far as I know: Synapse (controlled by Element), Dendrite (controlled by Element, and almost on par with Synapse according to https://arewep2pyet.com/ ), and Conduit. Based on https://gitlab.com/famedly/conduit/-/milestones/3 , Conduit seems to be far from implementing the spec yet (eg. it doesn't seem to support leaving rooms or respecting history visibility).

    > things like: server-side history extensions tended to mess up my client's history implementation (I'd end up with multiple copies of the same messages in my local logs, often with the wrong timestamps)

    You can use https://ircv3.net/specs/extensions/message-ids to deduplicate them.

    > And if you're in a conversation where people are using embedded gifs, then fundamentally you'll always be a second-class citizen if you're trying to participate in that with a client that can't display embedded gifs.

    A conversation where people where people are using embedded gifs will exclude me regardless of client, because they are too distracting. At least on IRC I can expect people not to do it too much, and use words or emojis instead of reaction gifs.

    > SSO access control; you just can't do that in a nice way if the client doesn't support it

    That's a fair point; IRC is made by hobbyists more than companies, so that's not surprising. There is some discussion around it though: https://github.com/ircv3/ircv3-ideas/issues/74 and Sourcehut is sponsoring implementation (https://emersion.fr/blog/2022/irc-and-oauth2/).

  • Matrix conduit server takes forever to join channels
    2 projects | /r/selfhosted | 17 Jan 2023
  • Looking to deploy a Conduit Matrix server. Is it possible to make a server which does NOT require a domain?
    2 projects | /r/selfhosted | 18 Dec 2022
    To start, this will be strictly Non-Federated. Just a few friends will be using this. Here: https://gitlab.com/famedly/conduit/-/blob/next/DEPLOY.md is the documentation I am following. It tells me I must "use my server name", but what is this exactly? What do I put in there? Do I have to go out and buy a domain?
  • Instant Messaging: XMPP or Websocket
    5 projects | /r/selfhosted | 5 Nov 2022
    Either Tinode (https://github.com/tinode/chat) or Matrix Protocol (https://gitlab.com/famedly/conduit)
  • Planning to make a video on cool Rust apps focused on the end user. Make recommendations!
    38 projects | /r/rust | 2 Nov 2022
    Matrix Protocol: Fractal (Client), Conduit (Server)
  • Discord-esk encrypted platform?
    3 projects | /r/privacy | 19 Oct 2022
    If self-hosting is an option then I'd say Matrix, you can try Conduit (server) and Elements(client). To simplify deployment you can refer to this repo.
  • anyone using rust in production? what do you do?
    22 projects | /r/rust | 30 Mar 2022
    You can babble on and on about how its not how you do it, no one needs it, etc... But its a demonstrable need in this space and its caused me great pain trying to write applications that would be used by such people. It's even bit Conduit to the point they have 5+ DB backends coded in now that the user can choose between based on their local system setups.
  • Is there an example app that uses Sled database in Rust?
    4 projects | /r/rust | 12 Mar 2022
    There's a Rust implementation of a Matrix server that uses sled: https://gitlab.com/famedly/conduit/
  • Is 'dendrite' ready to host your own Matrix server
    3 projects | /r/selfhosted | 29 Jan 2022
    Check out the Conduit 1.0 Release Milestone.
    3 projects | /r/selfhosted | 29 Jan 2022
    From Conduit.rs CI job report 2022-01-31 (redacted for brevity): ```

What are some alternatives?

When comparing Synapse and conduit you can also consider the following projects:

dendrite - Dendrite is a second-generation Matrix homeserver written in Go!

Rocket.Chat - The communications platform that puts data protection first.

Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.

Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..

matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker

Nextcloud - ☁️ Nextcloud server, a safe home for all your data

fluffychat

fosscord - 📬 Spacebar is a free open source selfhostable discord compatible communication platform [Moved to: https://github.com/spacebarchat/spacebarchat]

RetroShare - RetroShare is a Free and Open Source cross-platform, Friend-2-Friend and secure decentralised communication platform.

Mastodon - Your self-hosted, globally interconnected microblogging community

matrix-doc - Proposals for changes to the matrix specification [Moved to: https://github.com/matrix-org/matrix-spec-proposals]