Selfhosted

59778 readers

587 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Where is the love for conduit? Everybody is preferring continuwuity or tuwunel? (lemmy.world)

submitted 2 hours ago by mobergmann@lemmy.world to c/selfhosted@lemmy.world

6 comments fedilink hide all child comments

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, ....

you are viewing a single comment's thread
view the rest of the comments

[–] hendrik@palaver.p3x.de 1 points 2 hours ago* (last edited 2 hours ago) (1 children)

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.

[–] stratself@lemdro.id 1 points 57 minutes ago* (last edited 54 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 actively working on it.