

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.
Sit down. Let me pour you a drink. Then let us lament the curse of the normie together.
Beratna, tell me…is DeltaChat meeting their needs? Is it easier for you? I have one more migration in me, but i’m tired, Beratna. I just walked in to find my youngest (gasp) watching Netflix instead of the carefully curated media server.
Like a lot of us, I solved an interesting technical problem without accounting for the messy end user problem.
Fortunately, this one can be solved with a little uTorrent and some post-hoc market research and buy in (chocolate).
You saying Deltachat gets you more of that then XMPP and Conversations, I’m willing to listen.