Skip to content
What's new

Read receipts in DMs and group chats

  • In a DM, Seen appears under your latest message once the other person has read it; in a group chat, who has (Seen by Maya and Jonas), or Seen by everyone. Point at it for when. It changes live as people read.
  • A conversation counts as read while it's open on someone's screen, not while it sits in a background tab.
  • Each person can turn theirs off in Settings → Notifications (and then sees nobody's, as in Teams); admins can turn them off for everyone in Admin → General, which goes into the audit log. They show in conversations of up to 20 people; agents and other bots are never listed.
  • API: GET/POST /dm/seen/{user_uuid} and /groupChat/seen/{grp_id}, POST /admin/read-receipts, read_receipts in /user/notificationPreferences, MQTT message type 34. Migration 195.

The flow of work in Reports

  • Reports gain a cumulative flow chart: at the end of each week, the tasks to do (the backlog with them), in progress and in review, and what got done since the report began, as stacked bands. A band that keeps widening is work piling up at that step. It reads each task's history, so it covers the weeks before you updated too.
  • The report's JSON gains flow (one entry a week, lined up with weeks).

Fixes

  • Live updates in the browser work again. Since v2.64.0 the web app loaded its live-connection library late, and in production builds that load found no connect: new messages, typing and other live changes didn't show until a reload. The web app was fixed on its branches on 8 October; run make web_up (or make update), or redeploy your frontend, if you updated to v2.64.0 or v2.65.0.
  • A conversation's read mark only moves forward, so a Slack import's older times can't make read messages unread again; and a new conversation no longer starts out as read by the people it was sent to.
  • Two settings saved in Admin were never read back: the audit log's retention window and the push notification credential. Both now apply (they used the environment's values instead).
  • Search no longer loses one of two changes made to the same item at once (OpenSearch version conflicts are retried).
v2.66.0 with AI · v1.51.0 without AI