Comment on (XMPP Setup Guide) Discord Was Never the End Game - TonyBTW
AHorseWithNoNeigh@piefed.social 1 day agoThat github looks like a fork of the original code. I never heard of fluxer so I can’t really trust it since I’ve only ever heard people gathering opinions rather than reviews, a fork even less so. So for my honest opinion, it’s a no for me since it seems like a very round about way to onboard anyone who wants to self-host.
Since we’re here, I’ve tried giving stoat.chat a go and got it semi-working but the way they have the project set up, there’s a lot of optional “bloat” that gets tacked on from the build.
What I had success with, was Continuwuity. Their docs were so good, I was not only able to set up chat but also new and legacy voice and video under 4 hours.
chortle_tortle@mander.xyz 1 day ago
Yeah that is yucky, seems like self hosting hasn’t really been at the forefront of intention for the project. From the looks of it, them being in Sweden it might have started as a “buy EU” sort of discord clone that was pulled into the death of discord conversation with the ID stuff.
Interesting times 🫠
Curious your thoughts on stoat, that came out of revolt correct? What sorts of bloat did you find?
4 is definitely a good benchmark for self hosting! lol Have you run Synapse, and how did that compare?
AHorseWithNoNeigh@piefed.social 23 hours ago
Sorry for the later reply, was working (oops, not really). From what I read, Stoat is just a rename of Revolt and the platform should really remain the same (when I had this up, some of the UI still read Revolt).
For the bloat, as a self-hoster (speaking for myself and not on the behalf of anyone else), you should try to be provided with the most direct solution to a specific issue. When looking at Stoat, and the output of the
generate_config.sh, they basically shove down a whole lot of solution at one time. There’s from what I can tell, 15 different configurations for containers, over half of them are static versions and who knows how they all intermingle between the configs. This produces a monstrous web of configuration that I really have no time to digest and get working for something I’m just ‘playing around with’. All this and I didn’t even attempt to integrate voice and video. Also (as a nitpick) requires you to spin up caddy but has a config to point to that to a different reverse-proxy if needed (I already had nginx proxy manager and got this working but the whole thing fails if you don’t spin up caddy. insert sad horse noises).This is where Continuwuity comes in, I have 4 containers that I have bespoke configured myself by reading the configs and 2 config files that I hand made based off the docs. I feel WAYYYY better at hosting this than Stoat. Even got the wife to help test the video and voice and it works great with Element.
I have hosted Synapse before and got it up and running but not with voice and video. IMO, it’s a little bloaty as well (not nearly as bad as Stoat) but it’s doable. Never attempted voice and video for this but again, Continuwuity is just much more straightforward and less overhead.
chortle_tortle@mander.xyz 22 hours ago
No worries, thank you for the detailed reply!
Sounds like a solid way to do it, and a support the uwuification of all software, so that’s an extra bonus! Might have to futz around with it and see what sort of mess I can get myself into.