40
submitted 1 week ago* (last edited 1 week ago) by smileyhead@discuss.tchncs.de to c/selfhosted@lemmy.world

I plan to host Conduit for my friends and family. Even if I invite absolutely everyone there would be no more than 50 users, max. But would it actually sustain and work, as it is not yet on 1.0 is a question. I do not want to host Synapse as I had bad time with it's (lack of) garbage collecting. We do not plan to join very big rooms.

Most importantly, if you host it yourself, host is the usage (mostly disk) with how many users?

you are viewing a single comment's thread
view the rest of the comments
[-] h3ndrik@feddit.de 12 points 1 week ago* (last edited 1 week ago)

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.

[-] mypasswordis1234@lemmy.world 3 points 1 week ago

Check out conduwuit. It is a fork of conduit and you can see all the differences here

[-] h3ndrik@feddit.de 2 points 1 week ago

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?

[-] mypasswordis1234@lemmy.world 3 points 1 week ago

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)

[-] h3ndrik@feddit.de 1 points 1 week ago

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.

[-] mypasswordis1234@lemmy.world 2 points 1 week ago

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.

[-] h3ndrik@feddit.de 1 points 1 week ago* (last edited 1 week ago)

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.

this post was submitted on 21 Jun 2024
40 points (97.6% liked)

Selfhosted

37715 readers
552 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS