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, …
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. SSO/Authentication integrations. And clients which can do multiple accounts.
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 actively working on it.