Skip to content

Save a message for later and be reminded about it (stage 1a: storage and firing) - #901

Draft
unRekable wants to merge 3 commits into
mainfrom
draft/790-reminders
Draft

unRekable wants to merge 3 commits into
mainfrom
draft/790-reminders

Conversation

@unRekable

@unRekable unRekable commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

What changed and why

A message can carry a reminder now, on the chatd side: "Remind me" sets a time, chatd keeps it
in its store, and when the time comes it posts one notification through the notifier it already
uses — silent, with the message's words and where it sits. A reminder survives a restart, fires
once, and is gone after it fired or was cancelled. Nothing goes to any network: the reminder is
the user's own ask. This is stage 1a of #790; the window's "Remind me…" menu item and picker are
stage 1b, on the wire this pull request adds and needing no further protocol change. The Later
list across networks stays stage 2.

Type

  • feature
  • fix
  • perf
  • refactor
  • chore
  • docs

Platforms

  • windows
  • macos
  • linux
  • android
  • ios

Proof

Scenario: e2e/scenarios/message-remind

Lab run:

Compatibility

The wire only grew: Request::Remind, Request::Reminders, Response::Reminders, and
MessageReminder are new variants a peer that never sends them never sees; Remind.remind_at
is #[serde(default)] and left off when empty. An older chatd answers the new requests with an
error, which the window shows. The store grew one table, created IF NOT EXISTS on every open
with no schema-version change and named in the rebuild drop next to settings, so a schema
bump rebuilds the cache and keeps reminders, and no shipped migration was edited.

Risk and rollback

chatd's notification thread computes its sleep from the store instead of sleeping for events
alone: one indexed min(due) per event, capped, and no change to how it handles what arrives.
If it misbehaves, reverting the pull request removes the table's reads and writes; the table
itself is inert rows that no older build touches. The cap (256 per account) bounds the table.
Reminders fire only while chatd runs; #802's quit notice should say so.

Release note

Reminders: keep a message on your mind — a reminder on a message tells you about it at the time
you picked, even after a restart.

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