Skip to content

Recipients see a message only once it is sent - #54

Merged
markmnl merged 1 commit into
mainfrom
recipients-see-sent-only
Oct 17, 2026
Merged

markmnl merged 1 commit into
mainfrom
recipients-see-sent-only

Conversation

@markmnl

@markmnl markmnl commented Oct 17, 2026

Copy link
Copy Markdown
Owner

A draft's recipients could see it before it was sent:

  • GET /fmsg listed it;
  • they could read it and its data, attachments and thread;
  • they could mark it read, react to it and add recipients to it.

Clients that save drafts while their user types, as fmsg.ai's web app does, showed recipients empty and half-written messages that never stayed read (reported by users today).

A draft is now its sender's alone. GET /fmsg lists sent messages only, and every recipient route answers 404 for someone else's draft: get, data, attachment download, thread, thread/messages, read, react and add-to. The sender's own views are unchanged.

Tested: TestRecipientsCannotSeeDrafts (integration, Postgres) checks each route before and after send; the full suite passes.

🤖 Generated with Claude Code

A draft's recipients could list it in GET /fmsg and read it, its data,
attachments and thread, mark it read, react to it and add recipients to
it. Clients that save drafts as their user types (fmsg.ai's web app
does) showed recipients empty and half-written messages that could never
be marked read.

A draft is now its sender's alone: GET /fmsg lists sent messages only,
and every recipient route answers 404 for someone else's draft.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@markmnl
markmnl merged commit 53e1e7d into main Oct 17, 2026
1 check passed
@markmnl
markmnl deleted the recipients-see-sent-only branch October 17, 2026 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant