Skip to content

bridgev2: add disappearing message mode that starts after the recipient reads it - #565

Merged
iFixRobots merged 2 commits into
mainfrom
codex/recipient-read-disappearing-messages
Sep 9, 2026
Merged

iFixRobots merged 2 commits into
mainfrom
codex/recipient-read-disappearing-messages

Conversation

@iFixRobots

@iFixRobots iFixRobots commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Adds after_read_by_recipient for direct chats where a message's timer starts when its recipient reads it.

Outgoing messages wait for the other person's read receipt. Incoming messages wait for our own read receipt. The existing storage and scheduler handle expiry; after_read and after_send keep their current timer behavior.

Timer storage stays in the normal serialized event handler. There is no global capability, new completion hook, or separate transaction path.

Affected-package build, vet and existing tests pass locally. Earlier native checks confirmed recipient-read timing in both directions; this type-based revision has not yet been exercised end to end. Clients must recognize the new type before a connector exposes it.

@tulir tulir changed the title Start DM disappearing timers when the recipient reads bridgev2: add disappearing message mode that starts after the recipient reads it Sep 9, 2026

@tulir tulir left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks about right

@iFixRobots
iFixRobots merged commit 8ebe145 into main Sep 9, 2026
10 checks passed
@iFixRobots
iFixRobots deleted the codex/recipient-read-disappearing-messages branch September 9, 2026 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants