this post was submitted on 23 Oct 2025
620 points (99.1% liked)
Selfhosted
60366 readers
565 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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
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.
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!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Its true.
It comes up at work, it comes up in discussions on Linux podcasts I listen to, it comes up here...
We have a big, dangerous impending problem in DNS.
The issue here isn't DNS. The issue here is a large portion of the internet relying on a single data centre on the US East coast. Ideally, a lot of competing hosting companies would exist so if one goes down, it's just one service and very few people notice.
So much this.
Why is Signal hosted in one location on AWS, for example? That's the sort of thing that should be in multiple places around the world with automatic fail over.
I prefer end to end encrypted xmpp
I prefer face to face communication, speaking in code and whispering in eachother's ears so nobody else can hear.
Get a little tongue in there, maybe.
I hope they work towards mitigating this risk from now on.
Yes, that's true, I guess it's a separate issue. But the way DNS currently runs is a problem waiting to happen.