this post was submitted on 11 May 2025
111 points (86.3% liked)
Selfhosted
60366 readers
701 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
That's not exactly true.
That said, you do need some form of centralized service to connect peers, but you can federate those. It's only job would be to connect peers, and a STUN server w/ TURN fallback is usually the approach here. These instances don't need to store any data long term, they just need to connect peers, and the client is free to choose any instance they want, or host their own.
That's how Tor works (entry nodes), and most decentralized systems use a similar system.
One of the best parts here is that offline often just works, and you can sneakernet around firewalls (e.g. if you visit China or something), and all you need to do is connect to a local relay to find local peers.
My understanding is it's only used for name resolution, so the number of data points here should be in the thousands, not millions or billions, so the resource usage should be minimal.
Basically, the blockchain is functioning as DNS here.