README: add why relaydns?
Kim committed
Oct 21, 2025 at 21:47 UTC
3c86b10535e9a1caffd192b8897d0326d638bb61
1 file changed
+14
-2
README.md
+14
-2
@@ -5,6 +5,18 @@
5
It lets you expose and discover TCP services (like SSH, API endpoints, etc.) even behind NAT,
6
without depending on centralized reverse-proxy services.
7
8
+## Why RelayDNS?
9
+Traditional DNS and hosting rely on centralized servers and public IPs.
10
+RelayDNS removes that dependency — making connections open, direct, and owned by the users themselves.
11
+
12
+This means:
13
+- No middlemen or fixed infrastructure.
14
+- Anyone can share or host freely.
15
+- Discovery remains open, but communication stays truly peer-to-peer.
16
+
17
+In a decentralized world, RelayDNS turns DNS from a naming system for servers into a discovery network for people —
18
+keeping coordination simple, while ownership and control stay entirely in your hands.
19
+
20
## Features
21
22
- **Peer-to-peer routing** over libp2p (supports hole punching, relay, pubsub)
@@ -48,7 +60,7 @@ Clients are NOT required to run the server. They are provided for testing/demo.
60
# make client-run BACKEND_PORT=8081 SERVER_URL=http://localhost:8080
61
```
62
51
-- Chat client (optional): WebSocket chat UI (local) + advertiser (libp2p). Uses coder/websocket.
63
+- Chat client (optional): WebSocket chat UI (local) + advertiser (libp2p).
64
```bash
65
make chat-run
66
# Optional overrides:
@@ -114,4 +126,4 @@ Chat client flags (see `make chat-run`):
126
- Cloudflare DNS:
127
- Web UI/proxy (8080): can be proxied (orange cloud) if using HTTP/HTTPS
128
- libp2p (4001 tcp/udp): must be DNS only (gray cloud). Cloudflare proxy doesn’t support arbitrary TCP/UDP ports.
117
-- WebSocket: server proxies 101 and tunnels bytes; the chat backend allows any HTTP(S) Origin for demo. Restrict in production.
129
+- WebSocket: server proxies 101 and tunnels bytes; the chat backend allows any HTTP(S) Origin for demo. Restrict in production.
\ No newline at end of file