❯ no middleman
Browser to browser, encrypted end to end. No account, no cloud, no copy left on a server.
one-time code · read it out loud
…or the link
The four words never reach the server: only the leading number does. Keep this tab open until the transfers finish. Any number of peers can ride the same code, each on its own channel.
…or receive: type the code you were given
❯ no webrtc
This browser has no RTCPeerConnection, and the files travel
on one: there is no fallback through a server, on purpose.
Usual causes: a very old browser, Tor Browser, or WebRTC switched off in
the settings (media.peerconnection.enabled in Firefox, a privacy
extension in Chrome). Open the same link in Chrome, Edge, Firefox or Safari, or use the
CLI, which needs no browser at all.
❯ handshake…
type the code again
inbound
integrity discrepancy