You see exactly what your witness will see, before you send. Both paths ship; you choose, every single time.
Craftee · Davi feedback actioned (cheers = emoji+words, searchable) · 2026-07-12 21:40 WEDT · now
Davi's correction, and he's right: this was full sentences, which is too much like a message. It's not a message — it's a cheer. So the witness sends emoji and single words: 👀 · proud · 💪 · yes! — energetic, instant, universally positive. They can never type anything that reaches you.
Her whole keyboard, on her screen: search a feeling → tap what fits. The search only finds; it never sends what she typed.
The search box is the trick that makes "no free text" livable. Without it, a fixed list feels like a cage — she can't find the thing she means. With it, she types proud and gets every proud-shaped way to say it. She still cannot send a single word she wrote herself. The vocabulary is the guardrail: a witness may say I saw you, and I'm glad; a witness may never say where were you.
Designee named the risk plainly: an unblurred video of your body, sent to someone who knows you, is exactly what a controlling partner can pressure you into. "User preference" is only real if the preference is free. So the guardrails aren't a policy document — they're built into the surface:
Every one of those exists so the unblurred choice can only ever be offered by you, freely, once, to one person — never requested, expected, tracked, or noticed by its absence.
The copy is load-bearing — it's a promise the architecture has to earn. On the blurred path the screen says "a sharp copy: one was never made." That is only sayable because of blur-at-capture and destructive (never reversible) blur. If the pipeline ever uploads-then-blurs, that sentence becomes a lie told to a person about their own body — delete it rather than ship it.
On the unblurred path I say the opposite just as plainly: your face will be visible to Maya. No euphemism. If someone is going to send their body to another person, they deserve to read it in words, not infer it from a missing blur.
Send is never disabled above 78%. The interface informs; it does not overrule. Davi granted the right to blur further, and blocking the button would be quietly taking it back.