Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

conduit.rs

Post reply on HN
Print view View original

41–50 of 193 posts

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

#41

Post by freeopinion »

nine_k wrote: post #31
ruslan wrote: post #27

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

There's the least common denominator XMPP, with a lot of key functions under optional XEPs. Thus the user experience is very uneven across clients and servers. Matrix has a more defined set of important features, so you could expect that conforming clients all implement them uniformly, without surprises.

Funny, I recently got pretty frustrated looking for a decent Matrix client. Not even Element claimed to support the full list of features on the Matrix website. And Element has super bizarre behavior like not allowing to paste into the message composer. And good luck getting help when a client doesn't work.

That said, I can't claim XMPP clients are any better.

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

#42

Post by jazzyjackson »

vkbjlnjknbj wrote: post #21
somenewaccount1 wrote: post #9

Earlier quoted context omitted.

Since every matrix server requires you create its own user id, I never understood the benefit of being federated.

it works the same way email does. you can use a mozilla.com user id to talk to someone with a matrix.org user id, or a kde.org user id all servers are equal participants in rooms, so a room doesn't live on a specific server aside from servers being able to create friendly names pointing to them, but nothing stops #foo:kde.org from pointing to the exact same room as #bar:mozilla.org -- both servers are participating e…

I can federate message across hosts, fine, but I can't move my username to another host, so it doesn't work like email, because with email the namespace is defined at the DNS level, and I just forward requests to whatever email host I want to use.

Being able to leave one server and join another while maintaining an identity (say, a public key for instance) is on Matrix's to do list, they haven't decided how to do it yet afaik.

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

#43

Post by ashton314 »

I’ve run a self-hosted Conduit instance for some years now. Pros: easy to install and use. Cons: it’s beta software!

That said, it’s been really good for me. Reliable chat between my and a few friends, plus some big-ish rooms that I participate in.

The author also works on Veloren[1]—another fun Rust project!

[1]: https://veloren.net

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

#45

Post by COGlory »

robobro wrote: post #2

One thing I didn't like about Matrix: I had a single server with 3 or 4 other users. In a few months, the database ballooned to, like, 80GB. User-uploaded content, including text, was in the ballpark of 2 or 3GB. Is there any way to clear out the cache of data received from old servers, say, anything more than 2 weeks old, and re-retrieve it if needed?

Yes, it's room/concersation states taking up all the space, and you can compress them.

https://levans.fr/shrink-synapse-database.html

https://github.com/matrix-org/rust-synapse-compress-state

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

#46

Post by Arathorn »

jazzyjackson wrote: post #42
vkbjlnjknbj wrote: post #21

Earlier quoted context omitted.

it works the same way email does. you can use a mozilla.com user id to talk to someone with a matrix.org user id, or a kde.org user id all servers are equal participants in rooms, so a room doesn't live on a specific server aside from servers being able to create friendly names pointing to them, but nothing stops #foo:kde.org from pointing to the exact same room as #bar:mozilla.org -- both servers are participating e…

I can federate message across hosts, fine, but I can't move my username to another host, so it doesn't work like email, because with email the namespace is defined at the DNS level, and I just forward requests to whatever email host I want to use. Being able to leave one server and join another while maintaining an identity (say, a public key for instance) is on Matrix's to do list, they haven't decided how to do it…

https://github.com/matrix-org/matrix-spec-proposals/blob/keg... is how we’re doing it, and it’s being implemented currently in Dendrite.

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

#47

Post by Semaphor »

jazzyjackson wrote: post #42
vkbjlnjknbj wrote: post #21

Earlier quoted context omitted.

it works the same way email does. you can use a mozilla.com user id to talk to someone with a matrix.org user id, or a kde.org user id all servers are equal participants in rooms, so a room doesn't live on a specific server aside from servers being able to create friendly names pointing to them, but nothing stops #foo:kde.org from pointing to the exact same room as #bar:mozilla.org -- both servers are participating e…

I can federate message across hosts, fine, but I can't move my username to another host, so it doesn't work like email, because with email the namespace is defined at the DNS level, and I just forward requests to whatever email host I want to use. Being able to leave one server and join another while maintaining an identity (say, a public key for instance) is on Matrix's to do list, they haven't decided how to do it…

With webfinger, you should be able to do exactly that. Migration of accounts is not in E-Mail, but while email has mx servers, Matrix (and most nu-fed stuff, not sure about XMPP) should have webfinger support for that.

edit: Okay, not actually webfinger. But [0] has instructions for the `/well-known/matrix/server` way. It only talks about subdomains, but it should work across domains. Possibly also with the SRV header.

[0]: https://github.com/spantaleev/matrix-docker-ansible-deploy/b...

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

#48

Post by freeopinion »

shortrounddev2 wrote: post #18

When I tried Matrix I found a lot of super right wing tech people using it. The main reason I could ascertain most of them were using Matrix was because they had been banned by other chat platforms for their opinions

I've heard a lot of super right wing tech people also use email, cell phones, Twitter, and TikTok. I heard some of them drive Fords, too.

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

#49

Post by lightedman »

COGlory wrote: post #45
robobro wrote: post #2

One thing I didn't like about Matrix: I had a single server with 3 or 4 other users. In a few months, the database ballooned to, like, 80GB. User-uploaded content, including text, was in the ballpark of 2 or 3GB. Is there any way to clear out the cache of data received from old servers, say, anything more than 2 weeks old, and re-retrieve it if needed?

Yes, it's room/concersation states taking up all the space, and you can compress them. https://levans.fr/shrink-synapse-database.html https://github.com/matrix-org/rust-synapse-compress-state

That it generates that much cruft for something so simple is disappointing. How long does the compression bandaid work for?

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

#50

Post by Arathorn »

freeopinion wrote: post #41
nine_k wrote: post #31

Earlier quoted context omitted.

There's the least common denominator XMPP, with a lot of key functions under optional XEPs. Thus the user experience is very uneven across clients and servers. Matrix has a more defined set of important features, so you could expect that conforming clients all implement them uniformly, without surprises.

Funny, I recently got pretty frustrated looking for a decent Matrix client. Not even Element claimed to support the full list of features on the Matrix website. And Element has super bizarre behavior like not allowing to paste into the message composer. And good luck getting help when a client doesn't work. That said, I can't claim XMPP clients are any better.

Element is basically 3 different clients - web, ios and android are different codebases. Paste to composer should work on all of them tho! Meanwhile on mobile there is a new client called Element X which is a single codebase built on matrix-rust-sdk: https://element.io/blog/element-x-experience-the-future-of-e....

Classic Element should support every specced feature in Matrix tho, and tonnes of MSCs, so unsure what features you’d be missing. Meanwhile Element X is less featureful, but way more performant and stable (we’re aiming for better-than-telegram UX and perf).

Post reply on HN