Private Message Conversations: Step 1 Solution Assessment

Feature plan: Step 1 · Step 2 · Step 3 · Step 4

Original Query

Great job! Please merge it. And write Step 1 for a reply feature and conversation view for private messages. Use docs/fdp/FEATURE_DEVELOPMENT_PROCESS.md.

Understood Intent

The completed aggregate-user composer has been merged; assess the next private-message slice: viewing the exchanged messages with one counterpart and replying from that context.

Problem Statement

Private messages are currently split between Inbox and Sent, so a member cannot read or reply to a two-party exchange as one conversation.

Option A: Assemble conversations in the browser from Inbox and Sent

Load the existing two mailbox lists, group entries by counterpart in the browser, and reuse the existing composer for replies.

• Pros:

  • Minimizes server-side changes.

  • Reuses current message lists and encryption behavior.

• Cons:

  • Each mailbox's list limit can produce an incomplete conversation.

  • Client-side grouping duplicates ownership, ordering, and recovery behavior.

Option B: Add an identity-scoped conversation surface

Add one authenticated conversation view that presents both directions for a selected counterpart and includes the established encrypted reply composer.

• Pros:

  • Gives one canonical, correctly ordered two-party view.

  • Reuses the existing recipient-key, encryption, signing, draft, and local decryption contracts.

  • Supports a small vertical slice: open a conversation, read verified messages, and reply.

• Cons:

  • Requires a conversation query and clear bounded-history behavior.

Option C: Introduce stored conversation identifiers

Assign a conversation record or identifier to each message and build replies and views around that new model.

• Pros:

  • Can support future group conversations and richer thread metadata.

• Cons:

  • Adds schema, migration, and historical-message complexity beyond a two-party reply slice.

Recommendation

Choose Option B. A counterpart-scoped conversation view with the existing composer is the smallest viable vertical slice: an approved member opens a two-party exchange, verifies its encrypted messages locally, and replies using the same all-approved-key envelope flow. Step 2 should set the history bound and define counterpart authorization and unavailable-key recovery.