nether/vommet

Watch

Fork 0

[Future] Saved messages: a DM with yourself (Telegram-style) #97

New issue

Open

opened 2026-10-07 23:31:28 +00:00 by robocub · 1 comment

robocub commented

2026-10-07 23:31:28 +00:00

Member

Upstream check: nothing matching in Commet's issues, PRs or branches (searched "note to self", "saved messages", "message yourself", "self dm").

How hard is it?

Small. Matrix already allows it: m.direct is keyed by user ID, and your own ID is a valid key. The work is mostly making the current code not trip over "my DM partner is me".

What breaks if we just add it naively (checked against testing a1a21432 + SDK vommet-v6.1.1-ss.3):

Creating it. createDirectMessage → SDK startDirectChat(me) calls createRoom(invite: [me], isDirect: true). Inviting yourself fails, so the room can't be made that way. Instead: createRoom with no invite, preset: private_chat, encryption on, then addToDirectChat(me).
Finding it again. startDirectChat / getDirectChatFromUserId(me) would find it once it's in m.direct (it only looks at joined rooms, and you are joined), so a second tap reuses it. Good.
Calls. The room header's call button sends startCall(room, voice, userId: partner). With partner = me, that rings yourself. Hide call buttons when the partner is your own ID.
Name and avatar. In a 1-member room the SDK's computed name is "Empty chat" or similar. Show a fixed label ("Saved messages" / "Notes") and your own avatar with a bookmark badge. Rename stays allowed.
"Switch to/from DM" menu (directMessageCandidate) needs exactly 2 members, so it never offers it for a 1-member room. Fine — the self chat gets its own entry point instead.
Encryption. A room with only you still uses Megolm and shares keys with your own verified devices, so it reads on every device you've verified. Nothing to add. Unverified new devices won't decrypt old notes until key backup restores them — same as every other room.
Other clients. They see a normal private room with one member. Some list it under people (because of m.direct), some under rooms. Harmless either way.

Entry points: a pinned "Saved messages" row at the top of the DM list, and "Message yourself" on your own profile (today the profile's "Message" button calls startDirectChat on yourself and fails).

Telegram extras for later (not v1): "Save to Saved messages" in the message menu (forward a copy with a link back to the original), and share-to-Vommet from Android landing there.

Raised in the same discussion. Today:

The DM list (directMessageRooms) is one row per room. Two DM rooms with Alice give two "Alice" rows, with nothing to tell them apart.
Opening a DM from someone's profile picks existingRooms.first — which one depends on list order, not on which one is in use.
The SDK's startDirectChat picks the one with the newest message. Two code paths, two different answers.

This happens more than you'd think: both sides press "Message" at once, one side's client crashes during creation, an old DM was left and a new one made, or a bridge creates its own.

Proposed:

One row per person in the DM list. The row opens the room with the newest activity; unread counts add up across all of them.
When there's more than one, the row gets a small count and a dropdown (or a "Conversations" section on the person's profile) listing every room: name, last message, created date, encrypted or not.
Profile "Message" uses the same rule as the SDK (newest activity), so it's always the same room.
Optional "Merge" helper later: it can't actually merge history in Matrix, but it can post a pointer ("continued in …") and remove the old room from m.direct so it falls back to a normal room.
Group DMs (3+ people) stay separate rows; grouping is only for 1:1 rooms.
Your self-chat follows the same rule — several self rooms become one "Saved messages" row.

The grouping key is the m.direct user ID (getDirectMessagePartnerId), so it's a UI change in the list and profile code. The data model stays the same.

Open questions for the operator

Name: "Saved messages" (Telegram) or "Notes" or "Note to self"?
Should the self chat be created on first use only, or pinned in the list from the start (created when first opened)?
Grouped row: dropdown in the list, or only on the profile?

Tester request (10-07): "Can I DM myself like in Telegram?" — a "Saved messages" / note-to-self chat for personal notes, links and files you want on every device. Workaround today: make a private room and invite nobody. That works, but it shows up as a room, not in the DM list. Upstream check: nothing matching in Commet's issues, PRs or branches (searched "note to self", "saved messages", "message yourself", "self dm"). ## How hard is it? Small. Matrix already allows it: `m.direct` is keyed by user ID, and your own ID is a valid key. The work is mostly making the current code not trip over "my DM partner is me". **What breaks if we just add it naively** (checked against testing `a1a21432` + SDK `vommet-v6.1.1-ss.3`): 1. **Creating it.** `createDirectMessage` → SDK `startDirectChat(me)` calls `createRoom(invite: [me], isDirect: true)`. Inviting yourself fails, so the room can't be made that way. Instead: `createRoom` with no invite, `preset: private_chat`, encryption on, then `addToDirectChat(me)`. 2. **Finding it again.** `startDirectChat` / `getDirectChatFromUserId(me)` would find it once it's in `m.direct` (it only looks at joined rooms, and you are joined), so a second tap reuses it. Good. 3. **Calls.** The room header's call button sends `startCall(room, voice, userId: partner)`. With partner = me, that rings yourself. Hide call buttons when the partner is your own ID. 4. **Name and avatar.** In a 1-member room the SDK's computed name is "Empty chat" or similar. Show a fixed label ("Saved messages" / "Notes") and your own avatar with a bookmark badge. Rename stays allowed. 5. **"Switch to/from DM" menu** (`directMessageCandidate`) needs exactly 2 members, so it never offers it for a 1-member room. Fine — the self chat gets its own entry point instead. 6. **Encryption.** A room with only you still uses Megolm and shares keys with your own verified devices, so it reads on every device you've verified. Nothing to add. Unverified new devices won't decrypt old notes until key backup restores them — same as every other room. 7. **Other clients.** They see a normal private room with one member. Some list it under people (because of `m.direct`), some under rooms. Harmless either way. **Entry points:** a pinned "Saved messages" row at the top of the DM list, and "Message yourself" on your own profile (today the profile's "Message" button calls `startDirectChat` on yourself and fails). **Telegram extras for later (not v1):** "Save to Saved messages" in the message menu (forward a copy with a link back to the original), and share-to-Vommet from Android landing there. ## Related: grouping several DMs with the same person Raised in the same discussion. Today: - The DM list (`directMessageRooms`) is one row per room. Two DM rooms with Alice give two "Alice" rows, with nothing to tell them apart. - Opening a DM from someone's profile picks `existingRooms.first` — which one depends on list order, not on which one is in use. - The SDK's `startDirectChat` picks the one with the newest message. Two code paths, two different answers. This happens more than you'd think: both sides press "Message" at once, one side's client crashes during creation, an old DM was left and a new one made, or a bridge creates its own. Proposed: - **One row per person** in the DM list. The row opens the room with the newest activity; unread counts add up across all of them. - When there's more than one, the row gets a small count and a dropdown (or a "Conversations" section on the person's profile) listing every room: name, last message, created date, encrypted or not. - **Profile "Message" uses the same rule** as the SDK (newest activity), so it's always the same room. - Optional "Merge" helper later: it can't actually merge history in Matrix, but it can post a pointer ("continued in …") and remove the old room from `m.direct` so it falls back to a normal room. - Group DMs (3+ people) stay separate rows; grouping is only for 1:1 rooms. - Your self-chat follows the same rule — several self rooms become one "Saved messages" row. The grouping key is the `m.direct` user ID (`getDirectMessagePartnerId`), so it's a UI change in the list and profile code. The data model stays the same. ## Open questions for the operator - Name: "Saved messages" (Telegram) or "Notes" or "Note to self"? - Should the self chat be created on first use only, or pinned in the list from the start (created when first opened)? - Grouped row: dropdown in the list, or only on the profile?

robocub referenced this issue

2026-10-07 23:36:15 +00:00

DM list: one row per person when you have several DM rooms with them #99

robocub commented

2026-10-07 23:36:15 +00:00

Author

Member

On ice (operator, 10-07): Saved messages is a future task. The "several DMs with the same person" part is split into its own issue so it can be done sooner: see the new issue #99.

**On ice (operator, 10-07):** Saved messages is a future task. The "several DMs with the same person" part is split into its own issue so it can be done sooner: see the new issue #99.

robocub changed title from ~~Saved messages: a DM with yourself (Telegram-style), and one row per person when you have several DMs with them~~ to [Future] Saved messages: a DM with yourself (Telegram-style)

2026-10-07 23:36:15 +00:00

No Branch/Tag specified

main

fix/unifiedpush-distributor-picker

fix/space-avatar-viewer

feat/image-save-and-viewer

fix/sidebar-drag-desktop

feat/message-drafts

feat/forward-messages

fix/profile-menu-clear

fix/quick-card-status

feat/banner-panes

fix/quick-card-banner

sync/state

sync/testing

sync/topic/feat/multi-sfu

sync/topic/feat/room-calls

sync/topic/feat/room-calls-start

sync/topic/fix/room-list-duplicates

sync/topic/ci/xplat

sync/topic/feat/matrix-links

sync/topic/feat/msc3160-timestamps

sync/topic/feat/screenshare-audio-picker

sync/topic/feat/screenshare-audio-stereo

sync/topic/feat/whats-new

sync/topic/fix/android-screenshare-errors

sync/topic/fix/call-join-retry

sync/topic/fix/call-view-follow-replaced-stream

sync/topic/fix/room-view-dispose-races

sync/topic/fix/screenshare-audio-app-names

sync/topic/fix/screenshare-audio-wayland-order

sync/topic/fix/screenshare-desktop-no-apm

sync/topic/fix/screenshare-one-at-a-time

sync/topic/fix/startup-launch-test

sync/topic/perf/lazy-side-room-lists

sync/topic/feat/native-oidc

sync/topic/feat/quick-audio-output

sync/topic/feat/quick-profile-controls

sync/topic/feat/telemetry-call-leave

sync/topic/feat/telemetry-capture

sync/topic/feat/telemetry-errcode

sync/topic/feat/telemetry-exit-reason

sync/topic/feat/telemetry-native-trace

sync/topic/feat/telemetry-timeline

sync/topic/feat/voice-isolation

sync/topic/feat/voice-quick-controls

sync/topic/fix/android-onaddtrack-race

sync/topic/fix/telemetry-consent-look

sync/topic/feat/dm-toggle-and-menu-tooltips

sync/topic/feat/screenshare-audio-linux

sync/topic/feat/screenshare-audio-upstream

sync/topic/feat/telemetry

sync/topic/fix/accept-dm-invite

sync/topic/fix/profile-nickname-others

sync/topic/ci/integration-banners

sync/topic/ci/integration-mosaic

sync/topic/ci/integration-tests

sync/topic/feat/discover

sync/topic/feat/sliding-sync

sync/topic/feat/welcome-first-login

sync/topic/fix/banner-thumbnail-scale

sync/topic/fix/directory-empty-message

sync/topic/fix/image-fullres-cache

sync/topic/fix/missing-media

sync/topic/fix/notification-fallback

sync/topic/fix/room-preview-deleted

sync/topic/fix/startup-splash-until-loaded

sync/topic/fix/sticker-picker-resolution

sync/topic/fix/voip-late-joiner-tiles

sync/topic/perf/lazy-home-room-list

sync/topic/perf/postload-keep-ui-responsive

sync/topic/perf/startup-postload-queue

sync/topic/ci/flatpak

sync/topic/ci/fork-invariants

sync/topic/feat/banner-headers

sync/topic/feat/desktop-copy-selection

sync/topic/feat/gradient-themes

sync/topic/feat/media-mosaic

sync/topic/feat/personal-packs

sync/topic/feat/room-banners

sync/topic/feat/room-picker-search

sync/topic/feat/space-remove-room

sync/topic/feat/sso-first-login

sync/topic/feat/telegram-sticker-import

sync/topic/feat/voice-messages

sync/topic/fix/linux-app-id

sync/topic/fix/own-push-gateway

sync/topic/chore/branding

sync/topic/chore/fork-settings

sync/topic/ci/android-apk

sync/topic/ci/version-label

sync/topic/fix/commet-badges-display-only

feat/telemetry-crypto

sync/main

feat/whats-new

fix/directory-empty-message

feat/multi-sfu

feat/room-calls-start

testing

ci/xplat

feat/matrix-links

feat/msc3160-timestamps

feat/room-calls

feat/screenshare-audio-picker

feat/screenshare-audio-stereo

fix/android-screenshare-errors

fix/call-join-retry

fix/call-view-follow-replaced-stream

fix/room-list-duplicates

fix/room-view-dispose-races

fix/screenshare-audio-app-names

fix/screenshare-audio-wayland-order

fix/screenshare-desktop-no-apm

fix/screenshare-one-at-a-time

fix/startup-launch-test

feat/native-oidc

feat/quick-audio-output

feat/quick-profile-controls

feat/telemetry-call-leave

feat/telemetry-capture

feat/telemetry-errcode

feat/telemetry-exit-reason

feat/telemetry-native-trace

feat/telemetry-timeline

feat/voice-quick-controls

fix/telemetry-consent-look

perf/lazy-side-room-lists

feat/voice-isolation

fix/android-onaddtrack-race

ci/integration-banners

feat/dm-toggle-and-menu-tooltips

feat/screenshare-audio-linux

feat/screenshare-audio-upstream

feat/telemetry

feat/welcome-first-login

fix/accept-dm-invite

fix/profile-nickname-others

fix/startup-splash-until-loaded

perf/lazy-home-room-list

perf/postload-keep-ui-responsive

ci/integration-mosaic

ci/integration-tests

feat/discover

feat/sliding-sync

fix/banner-thumbnail-scale

fix/image-fullres-cache

fix/missing-media

fix/notification-fallback

fix/room-preview-deleted

fix/sticker-picker-resolution

fix/voip-late-joiner-tiles

perf/startup-postload-queue

ci/flatpak

ci/fork-invariants

feat/banner-headers

feat/desktop-copy-selection

feat/gradient-themes

feat/media-mosaic

feat/personal-packs

feat/room-banners

feat/room-picker-search

feat/space-remove-room

feat/sso-first-login

feat/telegram-sticker-import

feat/voice-messages

fix/linux-app-id

fix/own-push-gateway

ci/android-apk

chore/branding

chore/fork-settings

ci/version-label

fix/commet-badges-display-only

update-feed

feat/auto-update

docs/soundboard-spec

fix/splash-timeout-crash

ci/xplat-fix

ci/windows-release

ci/windows-preview

ci/windows

ci/sync-dep-report

fix/sticker-no-autofavorite

chore/register-gradient-themes

design/logo

bootstrap

keybinder

update-emoji

fix-url-previews

fix-flatpak

test-color-scheme-generation

widget-reliability

custom-themes

livekit-rust

test-disabled-notification-counts

stutter-test

improved-link-handling

platform/ios

rich-notifications-linux

fix/gif-search-input

test/voip-data-channel

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

nether/vommet#97

No description provided.

Rows
Columns