I run a small invite-only Matrix server for a handful of people, with federation turned off and the admin side reachable only over my Tailscale network. Your friends won’t need Tailscale at all. The usual pattern is a cheap VPS running a reverse proxy that faces the internet and passes traffic back to the box at home, so your NAS never gets opened up. Turning federation off also sidesteps most of the public-room and metadata worries people raised here, since it’s just your group. I also host Cinny next to it so there’s a web version nobody has to install, and I use it with SchildiChat Next on my phone to move files and notes between my PC and phone. For non-tech friends I’d point everyone at FluffyChat or the Cinny link and walk them through saving their recovery key on day one, because that’s where people get stuck.
Same same but no VPS here. I use Tailscale to reach the self hosted XMPP instance, which is containerized. Clients can only reach the XMPP server (directly when on LAN, as white listed devices on Tailscale when not).
It works. The bottleneck is Tailscale, weird issues with Android VPN automation switch over (something about my wife’s Samsung phone really does not like Tailscale. She’s also worried it increases battery drainage when left on) and the fact that using Tailscale instead of VPS is not the moral victory I had hoped for. There’s headscale I suppose, but then I have to deal with self signed certs and…then, and then and then…
It never ends. Problems never end.
I console myself with the fact I’ve made an E2E private family chat service that works without a public-facing server, yet remains accessible outside home with a click of a button. That’s a win.
The problem is that I want it to work as smoothly as a commercial chat service on a shoe string budget, on a Raspberry pi sipping 2W. That and the fact that I’m bloody minded enough to work on it until it does, beyond the point of sanity.
That’s a real win. A private family chat that never touches a public server is the part a lot of people give up on. I feel you on the Android side too. I ran AdGuard Home as DNS for my tailnet and chased a lot of phone issues back to Tailscale. The DNS override settings were finicky, and it never played nice with Android’s always-on VPN, so I ended up just starting the client by hand after every phone reboot. That’s a big reason the friends on my Matrix server don’t touch Tailscale at all and go through a VPS instead. If you want to chase the battery question, checking the phone’s battery stats for a few days would tell you whether Tailscale is really the culprit. And I relate to the “until it works, beyond the point of sanity” part more than I’d like to admit.
The problem is that I want it to work as smoothly as a commercial chat service on a shoe string budget, on a Raspberry pi sipping 2W. That and the fact that I’m bloody minded enough to work on it until it does, beyond the point of sanity.
You’ve summed up the entire glory and insanity of this sub in two meager sentences. Compression is over 9000.
Comments
I run a small invite-only Matrix server for a handful of people, with federation turned off and the admin side reachable only over my Tailscale network. Your friends won’t need Tailscale at all. The usual pattern is a cheap VPS running a reverse proxy that faces the internet and passes traffic back to the box at home, so your NAS never gets opened up. Turning federation off also sidesteps most of the public-room and metadata worries people raised here, since it’s just your group. I also host Cinny next to it so there’s a web version nobody has to install, and I use it with SchildiChat Next on my phone to move files and notes between my PC and phone. For non-tech friends I’d point everyone at FluffyChat or the Cinny link and walk them through saving their recovery key on day one, because that’s where people get stuck.
Same same but no VPS here. I use Tailscale to reach the self hosted XMPP instance, which is containerized. Clients can only reach the XMPP server (directly when on LAN, as white listed devices on Tailscale when not).
It works. The bottleneck is Tailscale, weird issues with Android VPN automation switch over (something about my wife’s Samsung phone really does not like Tailscale. She’s also worried it increases battery drainage when left on) and the fact that using Tailscale instead of VPS is not the moral victory I had hoped for. There’s headscale I suppose, but then I have to deal with self signed certs and…then, and then and then…
It never ends. Problems never end.
I console myself with the fact I’ve made an E2E private family chat service that works without a public-facing server, yet remains accessible outside home with a click of a button. That’s a win.
The problem is that I want it to work as smoothly as a commercial chat service on a shoe string budget, on a Raspberry pi sipping 2W. That and the fact that I’m bloody minded enough to work on it until it does, beyond the point of sanity.
That’s a real win. A private family chat that never touches a public server is the part a lot of people give up on. I feel you on the Android side too. I ran AdGuard Home as DNS for my tailnet and chased a lot of phone issues back to Tailscale. The DNS override settings were finicky, and it never played nice with Android’s always-on VPN, so I ended up just starting the client by hand after every phone reboot. That’s a big reason the friends on my Matrix server don’t touch Tailscale at all and go through a VPS instead. If you want to chase the battery question, checking the phone’s battery stats for a few days would tell you whether Tailscale is really the culprit. And I relate to the “until it works, beyond the point of sanity” part more than I’d like to admit.
You’ve summed up the entire glory and insanity of this sub in two meager sentences. Compression is over 9000.
OVER 9000!
I appreciate you, LewdLemon. Enjoy this DBZ earworm, sent with love.
https://www.youtube.com/watch?v=nB5FTZkfXDs
Maybe make it your Matrix / XMPP ring tone or something for maximum suffering.
Sign in to comment. Sign in