Comment on Self-hosting messenger infrastructure
Spite_By_Design_LLC@lemmy.dbzer0.com 1 week ago
XMPP hosted via Raspberry Pi.
The setup is:
- Prosody provides the XMPP server.
- Converse.js provides web client / PWA.
- Conversations for Android clients
- Coturn provides TURN services for calls and NAT traversal.
- Tailscale provides remote access without exposing the XMPP server directly to the public internet.
(nb: also configured Message Archive Management (MAM) for chat history, private multi-user chat rooms (MUC), HTTP File Upload for media, and Jingle signalling for audio/video calls).
The server remains accessible over our LAN. When away from home, family members connect through Tailscale (I really should just use Android actions to and geofencing to launch Tailscale, but on my kids devices, I just leave Tailscale enabled. I don’t think it hits the battery too hard).
Why? Because I get joy from hosting my own shit, having control over it, having it work when other stuff falls over. My stuff falls over too, but I know WHY and HOW to fix it, and that’s how I prefer it.
My goal is to replace all cloud based services we use and I’m about 85% of the way there.