Conduit Chat Server VS nheko

If you're talking about Element switching its contributions to Synapse from Apache to AGPL, the rationale is that folks who want to commercialise Synapse will either have to a) opensource their changes, b) pay for an AGPL exception from Element, c) use a different server (e.g. Apache-licensed Conduit from https://conduit.rs) or d) write their own server. This hardly feels like suffocating competition. - Source: Hacker News / 5 months ago

Reminder - https://conduit.rs/ Rust implementation of the matrix server stack. - Source: Hacker News / 6 months ago

Many who have causally read about Matrix and looked into running a homeserver have run across the reference implementation Synapse, which is (IMO only, pls no flame) a bloated python monstrosity. This turned me off for years. A second-gen (?) alternative written in Go called Dendrite is much lighter weight, but is lacking in some features last I looked. A couple of years ago, I found Conduit (https://conduit.rs/)... - Source: Hacker News / 9 months ago

In Conduit (https://conduit.rs) there is no default config path, in order to start Conduit, you need to specify the CONDUIT_CONFIG environment variable, which is the path to your config. This will typically be done in a systemd service. This has multiple benefits:. - Source: Hacker News / 11 months ago

Until now, Rust was only present in the Matrix ecosystem thanks to contributions by third-parties in the form of Conduit and Fractal. So this is pretty rad. Amongst these two, Conduit is the most important project imo. It's a Matrix home server, written from scratch in Rust. Source: about 1 year ago

Like almost every client out there it has no support for e2ee. I was happy to find https://nheko-reborn.github.io (I'm a KDE user so Qt apps are preferred). - Source: Hacker News / about 2 years ago

Https://nheko-reborn.github.io/ supports it too? - Source: Hacker News / about 2 years ago