Live data from Hacker News

Conduit: Simple, fast and reliable chat server powered by Matrix

conduit.rs

121–130 of 193 posts

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#121
post #116

Earlier quoted context omitted.

Yes, I use my Conduit instance for all my development work and also host a big Discord bridge on it (for https://veloren.net , which was mentioned in another comment).

Very nice! Sounds like AppService/bridge support is on par with Synapse at this point (and maybe has been for quite a while?) - any gaps to be aware of in that department?

Most bridges should just work, some require messing around a bit, also see https://news.ycombinator.com/item?id=36939480, I haven't debugged this yet.

You can find some bridge documentation here: https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.m...

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#122

Hello, I'm Timo and I started the Conduit project a few years ago. Feel free to ask some questions.

Hi Timo!

I've been using Conduit for 10 months now and I love it. Thank you so much for it!

I've two questions:

- Is there any concern to have with regards to its future when you finish university? You seem to be by far the most active contributor and I'm worried the project is still dependent on how much time you can afford to put into it;

- What is the best way for a Rust / Linux developer to do a first impactful contribution to Conduit? With 155 open issues on GitLab at the moment and no problem really standing out for me as a user, I don't know where to start :p

Thanks!

BTW I hope you land a great job; I'd happily recommend you where I work, but we don't have any office near Dortmund unfortunately… Feel free to reach out to me if Dortmund / remote is not a requirement.

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#123
post #97

Earlier quoted context omitted.

Would be nice to transfer identity to a new domain but leave the server the same, like we typically do with email.

Not understanding your claim... How can I "transfer identity" to a new domain in email? I can't move myusername@gmail.com to @outlook.com, nor can I move myusername@someisp.com to myusername@anotherisp.com .

Well, with email you can a) forward from one address to another b) set up an auto-reply (I've moved), c) copy your message history via imap/maildir/mbox-files. Ditto for address book(s).

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#124

Hello, I'm Timo and I started the Conduit project a few years ago. Feel free to ask some questions.

Hi Timo! I've been using Conduit for 10 months now and I love it. Thank you so much for it! I've two questions: - Is there any concern to have with regards to its future when you finish university? You seem to be by far the most active contributor and I'm worried the project is still dependent on how much time you can afford to put into it; - What is the best way for a Rust / Linux developer to do a first impactful c…

Thank you for the kind words!

1: I can't say how much time I will have for Conduit, but I think the project is in a good shape and I think it can reach a stable release without me working full time on it, but of course it will take longer.

2: I think a good way to start is to hang around in the Conduit Matrix room and see if any issues pop up. Often these are relatively simple things like "these logs should have more details" and are a good way to get started.

I will also use this opportunity to link my LinkedIn profile: https://www.linkedin.com/in/timokoesters/

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#125
post #27

Can someone please explain, why use Matrix while there's XMPP ?

Because summaries like this still stand up as of today:

https://news.ycombinator.com/item?id=8998290

> XMPP is great for what it was designed for. It doesn't work well with mobile, high packet loss & high latency connections. XMPP is talkative and bandwidth intensive - bad for limited data/battery applications. It also wasn't designed for today's 1 person multiple devices reality. Most XMPP servers let you log in multiple times but messages don't sync between clients and sometimes get delivered to the client the user isnt currently in front of.

> Also, sending files over XMPP has pretty much always sucked - there are a bunch of incompatible ways to do it and it's always been hit and miss depending on which client your chat partner was using, network topography, etc.

Also, overload of XEPs doesn't help the ecosystem. Too many optional extensions hinders interop. People expect more features in modern chat experiences than what XMPP was designed for, and that's what XEPs have tried to fix as a bandaid, with mixed results.

On top of that, the technology choices are par of the course for the time it was designed, and nowadays there are arguably better things. Devs are naturally driven to choose tech that makes their work nicer, if they enjoy it, so that means more stuff gets done for the newer platform, in this case. As an example, coincidentally, another HN post today was touching on one of those points - the need for a very advanced XML parser, as a typical one apparently wouldn't be enough:

https://news.ycombinator.com/item?id=36930196

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#126
post #85

Hello, I'm Timo and I started the Conduit project a few years ago. Feel free to ask some questions.

Do you use Conduit daily yourself? I'm wondering if it's stable for daily use.

I've used Conduit for about a year now with bridges and it works flawlessly. It doesn't have all features but a recent release added Spaces and end-to-bridge encryption (not as big of a deal when selfhosting server + bridges, but great nonetheless), so I'm not even sure what is still missing.

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#127
post #89

Earlier quoted context omitted.

Matrix has well maintained clients and the overall experience is smooth especially for non technical people. Source: I use XMPP and Matrix daily.

What XMPP client(s) are you using that are not well maintained? And why?

Dino and Gajim both crash frequently on Wayland (Sway in particular) due to GTK issues that I'm not expecting to be fixed any time soon. Gajim also gets very slow the longer it's open, can't recall if Dino was the same. Dino also has the usual GNOME-y issues of being over-simplified and lacking in customization and features. When I changed from Dino to Gajim I was shocked at all the stuff I could suddenly do, was weird to think both were XMPP clients.

Something with Gajim's features but using Qt would be pretty great potentially. GTK stuff also often has this horrible thing where it fades the window when unfocused, which gets really awful and unresponsive when things get laggy, also ruins screenshots. Never figured out how to turn it off. Part of the theme apparently, but GNOME also doesn't want you customizing/changing your theme. I'm just using Adwaita-dark usually.

Matrix clients aren't great either, but overall Nheko gives me less trouble and pain than Gajim, using both daily. irssi (IRC client) is kind of my gold standard for stability/performance/features with weechat being mostly okay too.

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#129
post #83
post #53

Earlier quoted context omitted.

From the first link: >I shrunk my homeserver database from 100GB to a little under 8GB, during a long maintenance cleanup. I run the compressor on a cron job. I've been running for 5 years with ~ a dozen people on my server, all federated, in multiple large rooms, didn't run into space issues until this year. On Linode $10 and then Hetzner 4 CPU. One thing to watch out for: disable registration. Otherwise spambots wi…

I feel registration is something which should come disabled by default and need to be explicitly enabled.

At least on Conduit and Dendrite that is the case iirc, but it's easy to forget to disable it once you register an account.

Re: Conduit: Simple, fast and reliable chat server powered by Matrix

#130

Is there a way to migrate from Synapse to this? I don't know if I can justify destroying 6 years of conversation history.

Not yet. There're plans to build migration tool for Synapse to Dendrite, but support for Conduit would need to be built in as well.

Either way, it's unknown how long it'll take.

The tracking issue for Synapse -> Dendrite migration is all I've found. https://github.com/matrix-org/dendrite/issues/1705

Post reply on HN