ulkesh

EDIT>> And apparently I’m not the only one who may have issues with their current methodologies for using docker compose: https://github.com/stoatchat/self-hosted/issues/176

EDIT 2>> I tried Stoat using their hosted service (not self-hosting), and it leaves a lot to be desired as it relates to roles/permissions. I figure it’s a good six months or more away from being a viable alternative to Discord. It’s a good start, though.

Thanks for the reminder of that!

I’ve heard of it, but hadn’t yet looked into it much. I see this: https://github.com/stoatchat/self-hosted . It seems promising, I just wish it was a simple docker compose file with parameters (such as domain name/config file volume path/etc), so I can easily run it on UnRAID. But it’s requesting I run a shell script to generate some configuration file which could have been simple docker compose parameters. Therefore, in its current form, it requires I run docker compose via a shell that has the repo cloned.

And in order to do it a more proper way, in my opinion, I’d have to alter the compose file to change the “volumes” for many of the defined services to point to UnRAID’s appdata location. Every bit of this could have simply been environment variables within the compose file. And it would be ideal if the compose file could be set up to allow for external docker services that already exist (such as mongodb, redis, and rabbitmq). And it should expect reverse proxy hosting by default, not be the exception, again in my opinion.

I get that it’s open source and I could submit a pull request to do all I’d want, I’m just looking for a quick alternative to Discord without this level of effort. None seem to exist currently, at least for self-hosting. So I’ll continue looking into this when I decide to put in the effort for it. But I do appreciate your suggestion and may indeed go down this path soon.

I know Teamspeak 6 is in beta, so I get it. But boy when I tried it, it was just awful. It took me literal minutes just to figure out how to disconnect from the voice server. They desperately need to hire someone for UX who has actual experience in, you know, design.

And getting Matrix (Synapse) to run is about as teeth-pulling as getting an Oracle database system to run back in 2001.

I don’t like what Discord is doing. And I’ll likely find some alternative if I can convince others to also join me, but there simply is no viable alternative that gives the exact level of experience that Discord does (from a feature point of view and a UI/UX point of view).

And yes, I’ve tried Fluxer. It’s a good start, but still needs a lot of work, which the maintainer says is ongoing (work such as making self-hosting viable, etc). While I like the UI/UX of Fluxer, I am concerned that its UI is effectively a direct copy of Discord from a few years ago and I don’t know if Discord would be legally able to do something about this. Perhaps it’s all fine, and if so, I wish Fluxer immense success at being that viable Discord alternative, and I will keep an eye on this project.

👍

Well when the crash happens and the screen shows an enormous amount of green artifacting, sure looks like a graphics driver and/or kernel issue to me. But yeah, I’m probably wrong because your experience is pristine. And the many hours of research I’ve done on this subject leads to the conclusion that there are issues with 6.13+ kernel, amdgpu driver, and Wayland, and especially if having more than one display connected (despite setting the refresh rates to the lowest common denominator).

But I’m sure I’m wrong and it’s something completely different. Thanks for the insight.

I run cachyos. I know that they like to tweak the kernel and change numerous settings which can make gaming less stable in my specific scenario. I think I’m going to just run everything via gamescope now since I seem to have the proper flags to make it just work without oddities for me (I liked being borderless, but that causes issues with some games, so I am avoiding that now). And then see if I get any crashes. If I continue to see crashes, hopefully recoverable this time, then I may stick with linux-lts kernel instead of using cachy’s.

Maybe AMD can put some resources into fixing RDNA3 instability with the latest kernels this year? I’ve had unrecoverable system crashes (no access to TTY, keyboard/mouse locked up) when gaming with RDNA3 on any kernel >6.12, and mostly on wayland, numerous times now. I don’t undervolt/overclock. And I’m only running a 7900XT (a 2+ year old card now).

I’m basically relegated to running either on the 6.12 kernel, or run everything with gamescope just to attempt to guarantee stability and recoverability from crashes. Gamescope “works”, but seems to run best using “-f” for fullscreen mode – anything else seems to have some quirkiness for me.