Bluetooth mesh, the chat kind
Every phone both listens and speaks, and floods each message to its neighbours. Messages split into 469-byte pieces; duplicates are dropped; undelivered mail waits for the recipient.
In 1860 the Pony Express carried a letter more than 1,800 miles in 10 days, rider to rider, with no wire between them. A mesh network does the same with radios. Your phone hands the message to the next phone, and that phone to the next.
No tower. No account. No company in the middle.
Try it below01 · send
Every radio repeats a new message once, lowers its hop count, and drops copies it has already seen. Bitchat allows 7 hops.
reached 24 of 26 radios in 6 hops
24 transmissions, 103 duplicate copies dropped
2 radios heard nothing. Raise the hop limit or the range, or add radios.
02 · live
The map above is a simulation. This one is made of the people on this page right now.
Join, and this page becomes a real node. It links straight to a few other visitors, browser to browser, and every line you type hops from one to the next until the hop count runs out.
what joining sends
The room is public. Every node on the path can read a line, so write nothing private.
03 · cut the line
A fail-safe network holds several paths and uses the best one that still works. Cut them one at a time.
Local Wi-Fi
← carrying your message · fast, same building
Internet, direct
QUIC over UDP, device to device
Internet, by relay
when a firewall blocks the direct path
Bluetooth
short range, hop by hop, no internet
LoRa radio
kilometres, short messages only
Real systems try every path at once and keep the first that answers (ICE, RFC 8445).
When none answers, the message is stored and carried later (Bundle Protocol, RFC 9171) — the digital saddlebag.
04 · test yourself
this page arrived by …. Each test runs only when you press it.
Sends one request to Cloudflare's public trace page, which reads back the address it saw.
Sends one small UDP packet each to Google's and Cloudflare's public STUN servers. They see your address.
Your browser lists Bluetooth devices in range. This page learns only the one you pick.
05 · manual
Every phone both listens and speaks, and floods each message to its neighbours. Messages split into 469-byte pieces; duplicates are dropped; undelivered mail waits for the recipient.
Built for lights and sensors: messages flood node to node, 384 bytes at most. Phones cannot relay in it; they join through a helper node.
Bluetooth adverts are unsigned. A Flipper Zero can mimic earbuds and a phone shows the pairing pop-up. A mesh must sign what it sends.
A backgrounded iPhone app drops its name from its advert. A mesh needs radios that stay awake: a small computer on a shelf.
Routers share one address among many devices. Calls go out; none come in. Hole punching gets around it — when it fails, a relay carries traffic.
Encrypted transport over UDP that survives moving from Wi-Fi to mobile. 3–5% of networks block UDP, so a TCP fallback stays.
An encrypted IPv6 network with no centre. Your address is made from your key. It rides on links that exist. It is not anonymous.
Private tunnels between your own devices. Headscale is the control server you run yourself.
Long-range radio for short messages: kilometres per hop, no licence, small cheap boards.
Signed notes passed through many independent relays. Lose one and the rest still carry your mail.
Two browsers can link directly over WebRTC data channels, with the same hole punching any peer-to-peer app uses. They need an introduction first: on this site, public Nostr relays pass a sealed offer and answer. Once the link is up the relays can vanish and it stays.
A mesh keeps messages private. It doesn't hide that you use it: anyone nearby with a scanner sees the adverts.
Authorities shut the internet down 313 times in 52 countries in 2025, the most on record.
Every phone both listens and speaks, and floods each message to its neighbours. Messages split into 469-byte pieces; duplicates are dropped; undelivered mail waits for the recipient.
Built for lights and sensors: messages flood node to node, 384 bytes at most. Phones cannot relay in it; they join through a helper node.
Bluetooth adverts are unsigned. A Flipper Zero can mimic earbuds and a phone shows the pairing pop-up. A mesh must sign what it sends.
A backgrounded iPhone app drops its name from its advert. A mesh needs radios that stay awake: a small computer on a shelf.
Routers share one address among many devices. Calls go out; none come in. Hole punching gets around it — when it fails, a relay carries traffic.
Encrypted transport over UDP that survives moving from Wi-Fi to mobile. 3–5% of networks block UDP, so a TCP fallback stays.
An encrypted IPv6 network with no centre. Your address is made from your key. It rides on links that exist. It is not anonymous.
Private tunnels between your own devices. Headscale is the control server you run yourself.
Long-range radio for short messages: kilometres per hop, no licence, small cheap boards.
Signed notes passed through many independent relays. Lose one and the rest still carry your mail.
Two browsers can link directly over WebRTC data channels, with the same hole punching any peer-to-peer app uses. They need an introduction first: on this site, public Nostr relays pass a sealed offer and answer. Once the link is up the relays can vanish and it stays.
A mesh keeps messages private. It doesn't hide that you use it: anyone nearby with a scanner sees the adverts.
Authorities shut the internet down 313 times in 52 countries in 2025, the most on record.
06 · shelf
Bluetooth mesh chat for iPhone and Android. Open source.
LoRa mesh on small boards, with a browser client over Bluetooth or USB.
One identity over many carriers: LoRa, TCP, serial. Works above 5 bits a second.
The key-addressed IPv6 overlay.
Run your own control server for Tailscale clients.
Dial a device by its public key; hole punching and relays included.
Messaging over Bluetooth, Wi-Fi or Tor.
The clearest long read on why two devices cannot simply connect.