this post was submitted on 10 Nov 2026
96 points (100.0% liked)

Selfhosted

63822 readers
348 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
96
Self-hosting messaging infrastructure (sh.itjust.works)
submitted 4 days ago* (last edited 4 days ago) by LewdLemon@sh.itjust.works to c/selfhosted@lemmy.world
62 comments fedilink hide all child comments
 

I've been using Signal for many years now, and it fulfils most of my messaging needs. But last year's AWS outage, which took it offline for almost a day, showed one of its many flaws: Signal is highly centralised and reliant on big tech infrastructure.

I was therefore wondering if I shouldn't start self-hosting my own messaging infrastructure - maybe not for my day-to-day needs, but as an emergency fallback for my closest friends and family, should Signal fail again or become unavailable or compromised (looking at you, EU Chat Control!).

My first thought was to self-host my own Matrix/Synapse server, which ticks a lot of boxes for me: end-to-end encryption, media sharing (pics, audio, videos, all that good stuff), high availability of mobile clients with modern UIs, potentially even audio/video calls. The latter is still giving me a headache since apparently, I need a TURN server to get this working properly, and I'm somewhat reluctant to open so many ports just for it to work...

What's your perspective on self-hosting messengers: which ones do you prefer? What is your primary motivation to do it? And how have you set it up?

you are viewing a single comment's thread
view the rest of the comments
[–] Andres4NY@social.ridetrans.it 5 points 4 days ago (1 children)

@benno Meanwhile Prosody remains awesome, and the Snikket fork makes it even better.

[–] aksdb@lemmy.world 6 points 4 days ago (1 children)

Snikket is more like a distribution than a fork. It’s basically prosody with plugins and and configs.

[–] corsicanguppy@lemmy.ca 2 points 4 days ago (1 children)

Ah, but container-impaired. That's too bad.

[–] lemmyvore@feddit.nl 2 points 4 days ago

You can install the stack in an LXC container and take snapshots instead. Incus makes managing that very easy.

App stack in a system container + snapshots is a different approach from stack of app containers that you provision/tear-down but it gets you most of the same advantages.

Bit of time needed to re-learn Docker concepts in another form but I think it's a good tool to have on your belt. Sometimes apps aren't available for Docker, or they ship very poorly made images, or you simply feel that a system container that you upgrade in-place is the better fit.

Oh and Incus can also do VMs (KVM) with the exact same command interface as for LXC so you get that option too at the cost of learning one tool.