Live data from Hacker News

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

conduit.rs

181–190 of 193 posts

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

#181
post #151

Earlier quoted context omitted.

> The author also works on Veloren That game is fucking cool. A couple years ago me and some friends compiled it for kicks and giggles to see what it was all about. To our surprise, the game ran silky smooth on my GTX 1050 Ti. We get into a lobby. We play for a half hour. We're just exploring (the map is barebones but has cool landmarks) when I realize that you can scroll to zoom out from your character. In a psychad…

From Veloren's home page: "Veloren is a multiplayer voxel RPG written in Rust. It is inspired by games such as Cube World, Legend of Zelda: Breath of the Wild, Dwarf Fortress and Minecraft." I love how pointing out that it's written in Rust is more important that describing what the game is about or inspired by. Classic open source project unsure of who's the intended audience.

Why does there have to be an audience, or why can't it be other people interested in Rust?

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

#182
post #33

Earlier quoted context omitted.

Isn't xmpp old style instant messaging? As in, if you miss a message because you had poor connection or the application wasn't running then it's gone? Matrix does not work this way.

XMPP supports delayed delivery. It works although I have had minor issues with it, especially if OMEMO is enabled. https://xmpp.org/extensions/xep-0203.html

I think it's mostly through server side archives that chat history is kept in sync between devices nowadays

https://xmpp.org/extensions/xep-0313.html

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

#183
post #172

Earlier quoted context omitted.

What would you say is your biggest frustration with Matrix's design as a protocol ? I have some of my own opinions writing bots and such but I'm curious about the perspective of a homeserver implementatiom maintainer.

I think the model of having all events form a giant graph is overengineered. They tried to cope with this by introducing things like "fast room joins", but I think they are flawed and treat the symptom rather than the cause of the problem. Servers should only replicate the very core part of a room and fetch remaining information on demand. But I'm working together with the Matrix team to improve this in the future. I…

The impression I got from using Ruma's bot SDK library was that bot clients needed to keep around a lot of state involved in syncing the room to handle new messages properly. Which largely lines up with what you said, although maybe it's possible I could have gotten away with a more lightweight solution since I wasn't making a stanalone client?

> It's annoying to work on logic for threads, spaces, read receipts, read receipts in threads and so on

Another impression I got was this was kind of an excessive amount of duplication (and other duplications) that could have been avoided had a bit more forethought been put into the protocol design, especially with how these features interact with the e2ee.

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

#184

Earlier quoted context omitted.

You don’t need to sign up to multiple servers, if you can use the ID you already have to talk with everyone on other servers. Just like with E-Mail or XMPP.

..."if you can" use the single ID attached to only one server which, if unavailable, takes your identity with it.

Even with /.well-known/matrix or SRV entries?

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

#185

Earlier quoted context omitted.

Does any Matrix client support voice/video calls other than Element (including Hydrogen as it shares Element Web's codebase)?

Hydrogen does not share a single line of Element Web’s codebase.

I must have got it confused with another client then. Wasn't there another lightweight one made by Element-the-company that reuses the react SDK?

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

#186
post #127

Earlier quoted context omitted.

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 wei…

Pidgin?

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

#187
post #163

Earlier quoted context omitted.

I used to use Pidgin and as for the why: I had used Pidgin for many years to AIM, MSN, etc.

Yeah, Pidgin has fallen behind significantly with regards to modern XMPP compliance. The developers are still working on Pidgin actively, but the focus is on a big rewrite of the foundations right now (3.0) so they can more easily support modern IM features.

I wish them luck, but considering their lack of manpower, by the time 3.0 comes out for "modern IM features", we'll probably have telepathic computers.

I was there when they had the famous video-voice branch.

Heck, I just checked: https://developer.pidgin.im/wiki/vvAPI?version=1

It was 15 (!) years ago :-)

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

#188
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.im crashes too frequently for my tastes. It also doesn't have an official Windows version. Gajim looks outdated and the update procedure broke several times (I know the authors are working hard to modernize it though).

iOS story is sad. Family used Snikket (thanks for your work on it) but it still dropped notifications even after following with issues and Prosody modules needed. (Monal seems to be okayish now).

Even Conversations.im seems stuck. I know everyone has their favorite missing feature but for me no reactions is the biggest.

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

#189
post #157

Earlier quoted context omitted.

> and is more like a team messenger like Mattermost or Zulip. if at all, Element is this. Matrix doesn't really care about what type of users the clients target

And that is my point. While I use Matrix, it is confusing by itself as you need the client, which was hosted as riot.im, now element, etc. For a newcomer this page is just as confusing whle it could be a great entry as it being so lightweight compared to the actual Matrix server. Some additional notes will help a lot.

I also lost contact with a Matrix user during the riot.im -> element.io switch, so I empathize. But I think the flexibility and interoperability of Matrix is worth the additional complexity. Allowing different clients can be a major boon to accessibility, as blind or sight impaired users can use their own specialized client. Not to mention adapting to device form factor. Traditional workstation, tablet, phone all have different needs.

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

#190

Earlier quoted context omitted.

Hydrogen does not share a single line of Element Web’s codebase.

I must have got it confused with another client then. Wasn't there another lightweight one made by Element-the-company that reuses the react SDK?

nope.
Post reply on HN