Connected — using the secret you entered. Disconnect to change it.
Files never touch this server. Cinder relays a few hundred bytes of
WebRTC handshake between you and the other person — once that opens
a direct connection between your two browsers, the actual file moves
peer-to-peer, encrypted end-to-end by WebRTC itself (DTLS).
Share this however you like (call, chat, in person) — whoever has it can connect to whoever else has it. Both sides use the same one, and both sides can send and receive once connected — no roles to pick.
Or pair automatically (recommended)
Each side generates a one-time key and you both derive the same
secret between you (ECDH) — nobody but the two of you ever
transmits it, and it's never reused for another transfer. The
cinder-standard pairing method — see D009 in this repo's own
plan — shared with cinderchat.
Send this link to the other person:
Waiting for them to open it…
Got a cinder link instead of the secret itself? Load it here
Or share it via a cinder link instead of the raw secret
With Generated key or Password, send the link and the
key/password over two different channels — an attacker who
only sees one of them still can't recover the secret.
Read once: whoever opens the link consumes it — if anything
goes wrong, it's just as easy to agree on the secret again as
to redo this step. Read up to 5: survives a chat app's own
link-preview crawler fetching the link before the real
recipient does (a real, observed problem — Discord's own
preview bot burning a read-once link before the intended
person ever clicked it) while still expiring quickly once
actually used.