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, …
Conduwuit (predecessor of Continuwuity and Tuwunel) hard-forked from Conduit and introduced breaking database changes. That is a significant people don’t easily “switch over”
I would say its pace of development is very slow compared to the pace of Matrix in general. But if you only want the barebones features, you can use it.
Feature-wise, Continuwuity offers email support, single-use registration token, policy server integration, user suspending, a ton more of admin commands, and some extra endpoints for Element Call. It is also actively working on OIDC-OAuth (so you can login with your IDP), and an ecosystem-wide Admin API. It also has an active community. I can’t speak for the other fork.
Lastly, I don’t think anyone “hate” conduit, the project is alright. It’s just not the topmost option.