Selfhosted
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- 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!
Firstly, I wish you the best of luck in your community's journey away from Discord. This may be a good time to assess what your community needs from a new platform, since Discord targeted various use-cases that no single replacement platform can hope to replace in full. Instead, by identifying exactly what your group needs and doesn't need, that will steer you in the right direction.
As for Element, bear in mind that their community and paid versions do not exactly target a hobbyist self-hosting clientele. Instead, Element is apparently geared more for enterprise on-premises deployment (like Slack, Atlassian JIRA, Asterisk PBX) and that's probably why the community version is also based on Kubernetes. This doesn't mean you can't use it, but their assumptions about deployments are that you have an on-premises cloud.
Fortunately, there are other Matrix homeservers available, including one written in Rust that has both bare metal and Docker deployment instructions. Note that I'm not endorsing this implementation, but only know of it through this FOSDEM talk describing how they dealt with malicious actors.
As an aside, I have briefly considered Matrix before as a group communications platform, but was put off by their poor E2EE decisions, for both the main client implementation and in the protocol itself. Odd as it sounds, poor encryption is worse than no encryption, because of the false assurance it gives. If I did use Matrix, I would not enable E2EE because it doesn't offer me many privacy guarantees, compared to say, Signal.
This quote from your link on the main client e2ee issues captures the zeitgeist of modern tech so beautifully:
Please keep in mind that this website is a furry blog, first and foremost, that sometimes happens to cover security and cryptography topics.
Forget about synapse and the "official" method. Install Continuwuity a matrix server written in rust, much much more efficient than synapse.
I took some notes while installing it here https://wiki.gardiol.org/doku.php?id=matrix%3Aconduwuit
I didn't use docker but directly installation is very easy, it's a single executable.
Oh man I need to look into this synapse is so slow
Iβll look into it, thanks.
Iβm still in the information gathering phase. Do you know if the element client works with the continuwuity server? Is it as easy as entering the domain, user, and password in the client?
Any client should be compatible with any server, if both are fairly up to date. Though, I never found a client nor server that are actually fully feature complete. The closest to that are synapse and element
I completely support you moving off of Discord, and I completely support you setting up Matrix. I tried a lot, I think it has the most feature parity. That being said, the biggest thing I regret when setting it up is that I went with Synapse for my backend Matrix server, when there are others.
I've heard very good things about Conduit (https://conduit.rs/), mostly that it's easier to stand up and easier to maintain.
Either way, I think it's a smart move, and it's worth the investment. It's not the easiest to stand up, but operationally our communication should be our own. Expect trial and error, getting one piece up and running, then the next, and then the next. Celebrate small wins like "Today I got it running" and then "Today I got federation working", and then "Now I have voice working!". Otherwise it's going to feel overwhelming.
I believe in the cause, so feel free to DM me if you have any questions, or send me a DM on Matrix :)
Oh, and a very useful tool - https://federationtester.matrix.org/
This will tell you exactly what is wrong with your federation.
12 pages of detailed documentation
Home Gamer: Is this it?
Fair criticism. I just donβt have a lot of free time. I can invest in Element but I wanted to crowd source information to see if it was worth it or if there was an easier way. It doesnβt get much easier than Docker
Or try yunohost. Once installed yunohost is managing ssl, domains, install and update matrix and other things if wanted.
Tuwunnel is a corporate-sponsored successor to Conduwuit.
I prefer Continuwuity which is a non for profit successor to Conduwuit.
Beside this, they are probably mostly the same
Which corporation sponsors Tuwunnel?
Idk but apparently the dev of tuwunel was a dick about the fork splitting.
Helm is what is used for real world software deployments. It has its problems but it's better than Docker Compose.
Out of curiosity, what makes it better?
A quick search says itβs a package manger for kubernetes. Besides plex, everything I selfhost is just for me. Would you say helm/kubernetes is worth looking into for a hobbyist who doesnβt work in the tech field?
Absolutely no. Kubernetes has it's benefits and it can make sense to get into it for tinkering etc, but if you just want to set up matrix and not learn an entire new system, stay away from it.
I need to agree here. K8s is only for the real tech savvy people. I'd you are just starting with docker avoid k8s or k3s.