Where is the love for conduit? Everybody is preferring continuwuity or tuwunel?

Submitted ⁨⁨2⁩ ⁨hours⁩ ago⁩ by ⁨mobergmann@lemmy.world⁩ to ⁨selfhosted@lemmy.world@lemmy.world⁩

I only read about people using continuwuity and tuwunel, but apparently none are using conduit. When searching, I only find “hate” against conduit, but no actual reason why people prefer the fork, except some ominous comments stating that it is practically unmaintained (which is not true). I found that conduit has the majority of features implemented, except minor things like threads (which is still WIP, to be fair) and presence. Also, it is rock solid, only using minimal resources. It may be slow in development, taking a bit longer to implement a new feature, but not too much longer. Or am I missing something the others have to offer?

If you are running a conduit fork, what is your reason for leaving conduit, and if you are running conduit, why didn’t you switch?

If it is not obvious: I mean compared to conduit and its forks, not synapse, …

source

Comments

Sort:hotnew top

litchralee@sh.itjust.works ⁨27⁩ ⁨minutes⁩ ago

some ominous comments stating that it is practically unmaintained (which is not true)

Objectively, I can see that the last commit to the default branch was in March 2026, and that the 10th newest commit was back in September 2025. Of these 10, 3 are new features and 6 are fixes and 1 is documentation. I also see in the issue tracker that no project developer replied to the two newest reports, which were reported 2 weeks and 2 months ago.

As a subjective opinion, the explanation that Conduit is essentially rock-solid and this doesn’t need much upkeep or commits, that is just not credible. The Git history shows fixes and new features, but at a rate that averages just one commit per month. And some of those commits are literally one-line changes.

But let’s suppose that the maintainers are uninterested in small UI or quality-of-life features, and only make changes when it crosses their threshold for what is “important” enough. That’s a choice, sure, but let’s see if that holds water. Here is the project’s response to an issue opened in January, with the response being in February that confirms a UI bug and schedules it for the next release.

That was three months ago. No updates. No mentioned branches or PRs or merges. All while this bug remains in place. And that’s understandable for FOSS project developers, for whom the project is not their day job.

But in any circumstances, the totality of the evidence does not inspire confidence, let alone a determination that Conduit is “rock solid”. And that’s even before looking at the code.

TL;DR: the premise of the question is wrong. Conduit is not maintained.

source
Shimitar@downonthestreet.eu ⁨2⁩ ⁨hours⁩ ago
To my knowledge conduit is basically dead in the water. Very little updates if any.

When I chooses my matrix server, o went with the predecessor of Continuwuity and then migrated to Continuwuity and have been happy ever since…

Tuwunnel don’t know, I didn’t really appreciated the corporate backing somehow and lack of perceived transparency.

Is conduit actually still in business at all?

source
hendrik@palaver.p3x.de ⁨1⁩ ⁨hour⁩ ago
I think it’s basically that. There’s new commits in the conduit repo. But it’s like one minor thing each other month. While other projects have a lot if activity and added a ton of features and MSCs. At the same time they’re equally as stable and possibly easier to use. So… Why not use one of them? You’ll get more features, quicker fixes for annoyances in Matrix. And I always wondered why Matrix doesn’t come with threaded conversations by default. And clients which can do multiple accounts.

source
- stratself@lemdro.id ⁨39⁩ ⁨minutes⁩ ago
  As to answer your questions, threaded conversations are mostly a client issue. The UX for them are still not very good so not a lot of people use it.
  
  SSO/Auth is actually quite hard to support. There’s the “legacy SSO” option which is deprecated in favor of native OIDC, and afaict only Synapse supports it for now. But Continuwuity is activeltly working on it.
  
  source