I installed it like 2 weeks ago. As of now it's still running and has a really low memory footprint compared to Synapse. But a lot of things aren't implemented. Chatting works fine. I get a lot of warning messages about not implemented things, though. Like my client (FluffyChat) trying to query some profile status ... I'd say try it. I've done so. But I can really only give some good advise after a few more weeks of using it. Maybe there is a dealbreaker.
this post was submitted on 21 Jun 2024
41 points (97.7% liked)
Selfhosted
39247 readers
260 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.
Resources:
- 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 1 year ago
MODERATORS
I found that. Seems it mainly addresses caching and database performance, adds some admin and moderation commands. I'm not sure if it addresses any of the shortcomings I have.
My main question is: Which one is going to be maintained in the years to come and have the latest features implemented? And secondly: Why a fork? Why don't they contribute their fixes upstream to Conduit?
The original developer is trying to do things slowly and stay with older versions of the dependencies, while the author of the fork is of the opinion that the dependencies should be updated to the latest versions and take advantage of their capabilities (such as performance improvements) which does not necessarily please the original author.
In addition, new features are implemented in the fork that are not present in the original project, because the author of the fork is pushing for rapid development (which doesn't mean it's a bad thing)
Oh well, seems both reasonable. Maybe I should switch before the projects diverge too much. Conduwuit seems pretty active. Hope it stays that way.
Do you happen to have a link where I can read the backstory myself? Thanks for the info anyways. Seems to be a good call.
The author of the fork declares 100 percent compatibility with the original project's database. As you move, the database structure will be changed (new fields will be added) to be compatible with the fork, but it will still also be compatible with the original project (which simply will not use these new fields).
I used conduwuit for a long time and it seemed very stable. Now I don't host my server anymore because my friend hosts his own server and lets me use it, so I have an account on his server.
Ah, nice. Alright. Thanks again. I'll see how I can do it. Unfortunately I've already set everything up, joined Rooms and connected a few bridges. I hope it doesn't break. I'll do a backup first. Seems reasonable and not that hard to upgrade.
I use Conduit for myself and a couple friends to chat while gaming. It was a bit finicky to setup with the TURN server, but once it was running it's been great. Even has sliding sync for Element X. Only thing I'm still struggling with is setting up Webhook notifications.
Conduit should run fine up to many hundreds of users on a single node as far as message passing goes. For the storage part, you'll only operate as well as your storage solution. I'd honestly expect to invest some money on that part if you want the system as a whole to operate well, because some of the Matrix message handling is synchronous to media if attached to a message.
Depends a bit on how much images and videos get shared. If its mainly used for chat by a bunch of people and a few gifs and stickers in-between, it shouldn't consume that much storage. But sure if you frequently share all your vacation photos, the cache is going to grow fast.
I use it and it works, that's all I can say.
Only for yourself or so you share?
If share, please say how well it use the disk.
I would share it but I don't know anyone else who even knows what it is, much less would want to use it. Sorry.
Sorry to hijack — does my server name need a tld at the end? I’ve received both a yes and a no thus far. My server name currently has no tld but I’m not sure if that is what is preventing me from federating, or if no tld is just bad practice or something.
No problem.
Overall, purely technically, no. This has to be the hostname of the computer the Conduit is running on. And it can be in the local network (LAN) with your own name.
But practically, yes. Because you must buy a domain name and point that domain to the server localtion (IP address). And the only global domain names available to register have TLDs :).
So, yes.
I’m still trying to understand this. I have “example.tld” but when configuring the server name, just used “example”, no tld
You’re saying that my server name in fact needs to be the full “example.tld”?
Thanks for the help.
Yes, your server needs to be full domain name. Otherwise, when typing a username (like @myusername:myserver.com) other servers would need to know where that myserver.com is.
Conduit needs to know it's domain Because it is part of usernames.
Definitely the whole server name. Other servers and clients can't guess that information. I think it's properly documented how to do it.
In the mariushosting tutorial I followed a tld was not used. https://mariushosting.com/how-to-install-synapse-on-your-synology-nas/ (Step 14)
Same for the conduit tutorial https://mariushosting.com/how-to-install-conduit-on-your-synology-nas/ (Step 12)
Ah, well I only read the official documentation on https://docs.conduit.rs/
I'm gonna take a look at this later.